[PATCH 0/2] regulator: fix documentation warnings

Jerome Brunet posted 2 patches 1 month ago
include/linux/regulator/driver.h  | 5 +++++
include/linux/regulator/machine.h | 2 --
2 files changed, 5 insertions(+), 2 deletions(-)
[PATCH 0/2] regulator: fix documentation warnings
Posted by Jerome Brunet 1 month ago
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

Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
---
Jerome Brunet (2):
      regulator: doc: add missing documentation for init_cb
      regulator: doc: remove documentation comment for regulator_init

 include/linux/regulator/driver.h  | 5 +++++
 include/linux/regulator/machine.h | 2 --
 2 files changed, 5 insertions(+), 2 deletions(-)
---
base-commit: 5ddc236d094d496bcd1e78aaa88bdde530073b6f
change-id: 20241023-regulator-doc-fixup-76550a978dd4

Best regards,
-- 
Jerome
Re: [PATCH 0/2] regulator: fix documentation warnings
Posted by Mark Brown 1 month ago
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