linux-kernel - Re: [PATCH v1] ASoC: tas2781: Fix the wrong step for TLV on tas2781

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: <175448346413.51650.7450659009173444382.b4-ty@kernel.org>
Date: Wed, 06 Aug 2025 13:31:04 +0100
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
Subject: Re: [PATCH v1] ASoC: tas2781: Fix the wrong step for TLV on
 tas2781

On Fri, 01 Aug 2025 10:16:18 +0800, Baojun Xu wrote:
> The step for TLV on tas2781, should be 50 (-0.5dB).
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: tas2781: Fix the wrong step for TLV on tas2781
      commit: 9843cf7b6fd6f938c16fde51e86dd0e3ddbefb12

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