Clients of cs_dsp can provide optional callback function pointers, in
a struct cs_dsp_client_ops. The client had to provide a pointer to a
struct even if it didn't implement any of the callbacks.

Commit 1 in this series changes that so the client doesn't have to
provide a dummy struct.

Commit 2 adds kunit tests cases for this.

Richard Fitzgerald (2):
  firmware: cs_dsp: Don't require client to provide a struct
    cs_dsp_client_ops
  firmware: cs_dsp: Add test cases for client_ops == NULL

 drivers/firmware/cirrus/cs_dsp.c                     | 6 ++++++
 drivers/firmware/cirrus/test/cs_dsp_test_callbacks.c | 1 +
 2 files changed, 7 insertions(+)

-- 
2.47.3

On Fri, 28 Nov 2025 10:21:30 +0000, Richard Fitzgerald wrote:
> Clients of cs_dsp can provide optional callback function pointers, in
> a struct cs_dsp_client_ops. The client had to provide a pointer to a
> struct even if it didn't implement any of the callbacks.
> 
> Commit 1 in this series changes that so the client doesn't have to
> provide a dummy struct.
> 
> [...]

Applied to

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

Thanks!

[1/2] firmware: cs_dsp: Don't require client to provide a struct cs_dsp_client_ops
      commit: af37511305c0da1d151cc9a1ee6077c2cbde4f1d
[2/2] firmware: cs_dsp: Add test cases for client_ops == NULL
      commit: 479b1f8d416501cc3c18b743b1cf63776934ada9

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