linux-kernel - Re: [PATCH v3] ASoC: cs-amp-lib: Add KUnit test for calibration helpers

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: <170967131688.228819.10804344071690892747.b4-ty@kernel.org>
Date: Tue, 05 Mar 2024 20:41:56 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: alsa-devel@...a-project.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH v3] ASoC: cs-amp-lib: Add KUnit test for calibration
 helpers

On Mon, 04 Mar 2024 14:37:05 +0000, Richard Fitzgerald wrote:
> Add a KUnit test for the cs-amp-lib library. This has test cases
> for cs_amp_get_efi_calibration_data() and cs_amp_write_cal_coeffs().
> 
> A KUNIT_STATIC_STUB_REDIRECT() has been added to
> cs_amp_get_efi_variable() and cs_amp_write_cal_coeff() so that the
> KUnit test can redirect these to test harness functions.
> 
> [...]

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 for calibration helpers
      commit: 177862317a98adde284233aee074fc6e6a51cf95

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