[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176772855363.328192.192529625158196380.b4-ty@kernel.org>
Date: Tue, 06 Jan 2026 19:42:33 +0000
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 v2 0/8] firmware: cirrus: cs_dsp: Add long-offset WMDR
blocks
On Wed, 31 Dec 2025 17:27:03 +0000, Richard Fitzgerald wrote:
> Version 3 of the WMDR file format introduces a new block type that has a
> 32-bit address offset.
>
> The first patch of this series adds the support to the cs_dsp driver.
>
> The rest of the series is adding KUnit tests for this.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/8] firmware: cs_dsp: Handle long-offset data blocks
commit: bc0305cb294c693b2762cf863324defb9e5175e5
[2/8] firmware: cs_dsp: test_bin: Run test cases with v3 file format
commit: afcbb0460e0a9f0e971512c66619fc649bdb86a6
[3/8] firmware: cs_dsp: test_bin: Make patch function a test parameter
commit: a01816edf11fc9e6c8216bc03870311ce2add5a2
[4/8] firmware: cs_dsp: mock_bin: Pass offset32 to cs_dsp_mock_bin_add_raw_block()
commit: 9e6f4c5b2d3af58390cf554ada9591935c5ac774
[5/8] firmware: cs_dsp: mock_bin: Add function to create long-offset patches
commit: 880f1eb5b95ccf250f567927462a7d3fa8f2a727
[6/8] firmware: cs_dsp: test: Increase size of XM and YM on Halo Core
commit: 6e60c6aa1e4b929f6fbb04dc9fa786aeaedf3693
[7/8] firmware: cs_dsp: test_bin: Run test cases on long-offset blocks
commit: 7fecf0bf1202599920d929704a3787291fc068db
[8/8] firmware: cs_dsp: test_bin: Add tests for offsets > 0xffff
commit: 211243b69533e968cc6f0259fb80ffee02fbe0ca
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
Powered by blists - more mailing lists