linux-kernel - Re: [PATCH v3 1/2] ASoC: dt-bindings: ti,tas2781: Add TAS2568/2574/5806M/5806MD/5830 support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176365633604.66643.15357865496661099696.b4-ty@kernel.org>
Date: Thu, 20 Nov 2025 16:32:16 +0000
From: Mark Brown <broonie@...nel.org>
To: tiwai@...e.de, Baojun Xu <baojun.xu@...com>
Cc: andriy.shevchenko@...ux.intel.com, 13916275206@....com, 
 shenghao-ding@...com, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, lgirdwood@...il.com, robh@...nel.org, 
 krzk+dt@...nel.org, conor+dt@...nel.org, devicetree@...r.kernel.org, 
 k-yi@...com, henry.lo@...com, robinchen@...com, will-wang@...com, 
 jim.shil@...rtek.com, toastcheng@...gle.com, chinkaiting@...gle.com
Subject: Re: [PATCH v3 1/2] ASoC: dt-bindings: ti,tas2781: Add
 TAS2568/2574/5806M/5806MD/5830 support

On Mon, 17 Nov 2025 18:21:52 +0800, Baojun Xu wrote:
> TAS5806M, TAS5806MD and TAS5830 is in same family with TAS58XX.
> TAS2568, TAS2574 is in family with TAS257X.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/2] ASoC: dt-bindings: ti,tas2781: Add TAS2568/2574/5806M/5806MD/5830 support
      commit: bb52dc1d0342a4d2dccbfb1aedda019b8415cce1
[2/2] ASoC: tas2781: Add tas2568/2574/5806m/5806md/5830 support
      commit: d5089fffe1db04a802b028c2ef4875be1ed452a3

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark