linux-kernel - Re: [PATCH 0/2] cs35l56: Log tuning unique identifiers during firmware load

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: <174731091732.350483.16049439719916983135.b4-ty@kernel.org>
Date: Thu, 15 May 2025 14:08:37 +0200
From: Mark Brown <broonie@...nel.org>
To: Simon Trimmer <simont@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH 0/2] cs35l56: Log tuning unique identifiers during
 firmware load

On Tue, 13 May 2025 13:39:22 +0000, Simon Trimmer wrote:
> These two patches introduce a log message when provisioning the cs35l56
> family of devices that uniquely identifies the firmware tuning.
> 
> Simon Trimmer (2):
>   ASoC: cs35l56: Log tuning unique identifiers during firmware load
>   ALSA: hda: cs35l56: Log tuning unique identifiers during firmware load
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: cs35l56: Log tuning unique identifiers during firmware load
      commit: 823a036f049f5ea4afc55a2bc2e7f80a1acdef4a
[2/2] ALSA: hda: cs35l56: Log tuning unique identifiers during firmware load
      commit: db13e3d58c682e0bfc08410e4961b23f4bdbc2e5

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