linux-kernel - Re: [PATCH] firmware: cs_dsp: test_bin_error: Use same test cases for adsp2 and Halo Core

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: <174009007007.2293478.14977304010488785265.b4-ty@kernel.org>
Date: Thu, 20 Feb 2025 22:21:10 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com, 
 linux-sound@...r.kernel.org
Subject: Re: [PATCH] firmware: cs_dsp: test_bin_error: Use same test cases
 for adsp2 and Halo Core

On Wed, 19 Feb 2025 15:21:32 +0000, Richard Fitzgerald wrote:
> Re-use the adsp2 test cases for the Halo Core test run. Before this the
> Halo Core kunit_case array was an empty placeholder.
> 
> 

Applied to

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

Thanks!

[1/1] firmware: cs_dsp: test_bin_error: Use same test cases for adsp2 and Halo Core
      commit: 2e2f89b184644f0e29f1ec0b4dcfd0361d2635cb

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