linux-kernel - Re: [PATCH v4 1/2] ASoC: tas2781: Support more newly-released amplifiers tas58xx in the driver

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <176052178677.20166.7273787337857943286.b4-ty@kernel.org>
Date: Wed, 15 Oct 2025 10:49:46 +0100
From: Mark Brown <broonie@...nel.org>
To: tiwai@...e.de, Baojun Xu <baojun.xu@...com>
Cc: andriy.shevchenko@...ux.intel.com, 13916275206@....com, 
 alsa-devel@...a-project.org, 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, jesse-ji@...com, will-wang@...com, 
 jim.shil@...rtek.com, toastcheng@...gle.com, chinkaiting@...gle.com
Subject: Re: [PATCH v4 1/2] ASoC: tas2781: Support more newly-released
 amplifiers tas58xx in the driver

On Thu, 02 Oct 2025 15:29:24 +0800, Baojun Xu wrote:
> TAS5802/TAS5815/TAS5828 has on-chip DSP without current/voltage feedback.
> 
> 

Applied to

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

Thanks!

[1/2] ASoC: tas2781: Support more newly-released amplifiers tas58xx in the driver
      commit: 53a3c6e222836a23e8e0693395584aefc456dca6
[2/2] ASoC: tas2781: Update ti,tas2781.yaml for adding tas58xx
      commit: 7e6cfa3e94cf8278ee3170dc0b81fc6db1287e28

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