linux-kernel - Re: [PATCH v2] firmware: cs_dsp: fix kernel-doc warnings in a header file

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: <176313773169.173018.7219075760763381025.b4-ty@kernel.org>
Date: Fri, 14 Nov 2025 16:28:51 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>
Cc: Richard Fitzgerald <rf@...nsource.cirrus.com>, 
 Simon Trimmer <simont@...nsource.cirrus.com>, 
 Charles Keepax <ckeepax@...nsource.cirrus.com>, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH v2] firmware: cs_dsp: fix kernel-doc warnings in a
 header file

On Tue, 04 Nov 2025 11:26:53 -0800, Randy Dunlap wrote:
> Use correct kernel-doc format to avoid kernel-doc warnings in
> nclude/linux/firmware/cirrus/cs_dsp_test_utils.h:
> 
> - mark one struct member as private: since the comment says that it is
> private
> - add ending ':' to struct members where needed
> 
> [...]

Applied to

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

Thanks!

[1/1] firmware: cs_dsp: fix kernel-doc warnings in a header file
      commit: 8d63e85c5b50f1dbfa0ccb214bd91fe5d7e2e860

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