linux-kernel - Re: [PATCH] ASoC: cs-amp-lib: Add KUnit test case for empty calibration entries

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: <172503805409.196534.11009418066889155786.b4-ty@kernel.org>
Date: Fri, 30 Aug 2024 18:14:14 +0100
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: cs-amp-lib: Add KUnit test case for empty
 calibration entries

On Fri, 30 Aug 2024 15:48:19 +0100, Richard Fitzgerald wrote:
> Add a test case for commit bb4485562f59 ("ASoC: cs-amp-lib: Ignore
> empty UEFI calibration entries").
> 
> Any entries in the calibration blob that have calTime==0 are empty
> entries. So they must not be returned by a lookup.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs-amp-lib: Add KUnit test case for empty calibration entries
      commit: 99c9767c0444098a806529204c7a2556f89d0c04

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