linux-kernel - Re: [PATCH v1] ASoC: tas2781: Put three different calibrated data solution into the same data structure

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: <177028949673.8656.17097040591980827147.b4-ty@kernel.org>
Date: Thu, 05 Feb 2026 11:04:56 +0000
From: Mark Brown <broonie@...nel.org>
To: tiwai@...e.de, Shenghao Ding <shenghao-ding@...com>
Cc: andriy.shevchenko@...ux.intel.com, linux-kernel@...r.kernel.org, 
 baojun.xu@...com, Baojun.Xu@....com, 13564923607@....com, 
 13916275206@....com, matthew.schwartz@...ux.dev, lkml@...heas.dev
Subject: Re: [PATCH v1] ASoC: tas2781: Put three different calibrated data
 solution into the same data structure

On Mon, 02 Feb 2026 18:27:56 +0800, Shenghao Ding wrote:
> TAS2781 driver supports three solutions of calibrated data. The first is
> from the driver itself: driver reads the calibrated files directly during
> probe; The second is from user space: during init of audio hal, the audio
> hal will pass the calibrated data via kcontrol interface. Driver will
> store this data in "struct calidata" for use. The third is from UEFI,
> mainly used in hda device. These three solutions save the calibrated data
> into different data structures. It is time to put them together into
> "struct calidata" for use.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tas2781: Put three different calibrated data solution into the same data structure
      commit: 55137f5a68b5e888504ad36d07221cd749bb8956

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