linux-kernel - Re: [PATCH v1] ASoC: tas2781: Correct the wrong chip ID for reset variable check

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: <176400229349.72424.1392117575410206186.b4-ty@kernel.org>
Date: Mon, 24 Nov 2025 16:38:13 +0000
From: Mark Brown <broonie@...nel.org>
To: Baojun Xu <baojun.xu@...com>
Cc: tiwai@...e.de, 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, k-yi@...com, 
 henry.lo@...com, robinchen@...com, will-wang@...com
Subject: Re: [PATCH v1] ASoC: tas2781: Correct the wrong chip ID for reset
 variable check

On Mon, 24 Nov 2025 11:15:42 +0800, Baojun Xu wrote:
> The new variable of reset was added for TAS58XX on TAS5825 first.
> And TAS5802/5815... was added later, so this reset variable check
> should be changed to lowest chip of TAS58XX.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: tas2781: Correct the wrong chip ID for reset variable check
      commit: 34b78ddd78428e66a7f08f71763258723eae2306

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