linux-kernel - Re: [PATCH] firmware: cs_dsp: Fix kerneldoc typos in cs_dsp_mock

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: <173436195019.77772.5543212109898121281.b4-ty@kernel.org>
Date: Mon, 16 Dec 2024 15:12:30 +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, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] firmware: cs_dsp: Fix kerneldoc typos in
 cs_dsp_mock_bin.c

On Mon, 16 Dec 2024 10:55:20 +0000, Richard Fitzgerald wrote:
> 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