linux-kernel - Re: [PATCH 0/2] regulator: fix documentation warnings

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: <172969070684.51329.16819683295655789203.b4-ty@kernel.org>
Date: Wed, 23 Oct 2024 14:38:26 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Stephen Rothwell <sfr@...b.auug.org.au>, 
 Jerome Brunet <jbrunet@...libre.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] regulator: fix documentation warnings

On Wed, 23 Oct 2024 10:35:42 +0200, Jerome Brunet wrote:
> This patchset fixes the documentation warning introduced with the following
> series:
> 
> https://lore.kernel.org/lkml/20241008-regulator-ignored-data-v2-0-d1251e0ee507@baylibre.com
> 
> 

Applied to

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

Thanks!

[1/2] regulator: doc: add missing documentation for init_cb
      commit: e55f45b0cda71ac2e9b4c6dee8852dc8d6f22ef0
[2/2] regulator: doc: remove documentation comment for regulator_init
      commit: d1bc2d5cca434e7c854fd16ef021c16d74293b60

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