linux-kernel - Re: [PATCH 1/2] regulator: of: Fix kernel-doc

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]

Date:   Mon, 19 Sep 2022 17:49:57 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com,
        Jiapeng Chong <jiapeng.chong@...ux.alibaba.com>
Cc:     Abaci Robot <abaci@...ux.alibaba.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] regulator: of: Fix kernel-doc

On Mon, 19 Sep 2022 10:48:29 +0800, Jiapeng Chong wrote:
> drivers/regulator/of_regulator.c:689: warning: expecting prototype for of_parse_coupled regulator(). Prototype was for of_parse_coupled_regulator() instead.
> 
> 

Applied to

   broonie/regulator.git for-next

Thanks!

[1/2] regulator: of: Fix kernel-doc
      commit: 7ec12d153998616d9f9fd0e603d56b5e122fc768
[2/2] regulator: of: Fix kernel-doc
      commit: 7ec12d153998616d9f9fd0e603d56b5e122fc768

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