Skip to contentSkip to conversation

firmware: cs_dsp: Fix kerneldoc typos in cs_dsp_mock_bin.c

PATCH In review Richard Fitzgerald 2 participants 2 messages Dec 16, 2024

Subsystems (2)
lore
Share & tools
lore

Richard Fitzgerald

author maintainer
#0 lore raw

PATCH 1/1 firmware: cs_dsp: Fix kerneldoc typos in cs_dsp_mock_bin.c

Fix two places in kerneldoc where alg_id had been mistyped as alg_ig.

Fixes 7c052c661529 ("firmware: cs_dsp: Add mock bin file generator for KUnit testing")
---
 drivers/firmware/cirrus/test/cs_dsp_mock_bin.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/firmware/cirrus/test/cs_dsp_mock_bin.c +2 -2
index 1e271ccfd9b0..49d84f7e59e6 100644
@@ -53,7 +53,7 @@ EXPORT_SYMBOL_NS_GPL(cs_dsp_mock_bin_get_firmware, "FW_CS_DSP_KUNIT_TEST_UTILS")
  * cs_dsp_mock_bin_add_raw_block() - Add a data block to the bin file.
  *
  * @builder:		Pointer to struct cs_dsp_mock_bin_builder.
- * @alg_ig:		Algorithm ID.
+ * @alg_id:		Algorithm ID.
  * @alg_ver:		Algorithm version.
  * @type:		Type of the block.
  * @offset:		Offset.
@@ -139,7 +139,7 @@ EXPORT_SYMBOL_NS_GPL(cs_dsp_mock_bin_add_name, "FW_CS_DSP_KUNIT_TEST_UTILS");
  * cs_dsp_mock_bin_add_patch() - Add a patch data block to the bin file.
  *
  * @builder:		Pointer to struct cs_dsp_mock_bin_builder.
- * @alg_ig:		Algorithm ID for the patch.
+ * @alg_id:		Algorithm ID for the patch.
  * @alg_ver:		Algorithm version for the patch.
  * @mem_region:		Memory region for the patch.
  * @reg_addr_offset:	Offset to start of data in register addresses.
Signature · 1 line
2.39.5
#1 lore raw
Quoted 3 lines · Richard Fitzgerald

Fix two places in kerneldoc where alg_id had been mistyped as alg_ig.

Applied to

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

Thanks!

[1/1] firmware: cs_dsp: Fix kerneldoc typos in cs_dsp_mock_bin.c

      commit: 539a3f0c99cf62c61edc37a8f88e3073119ae852

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