linux-kernel - Re: [PATCH] regulator: mcp16502: add enum MCP16502_REG

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: <167405373960.864083.14418700342230230973.b4-ty@kernel.org>
Date:   Wed, 18 Jan 2023 14:55:39 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>
Cc:     Andrei Stefanescu <andrei.stefanescu@...rochip.com>,
        Claudiu Beznea <claudiu.beznea@...rochip.com>,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] regulator: mcp16502: add enum MCP16502_REG_HPM
 description

On Mon, 16 Jan 2023 23:01:39 -0800, Randy Dunlap wrote:
> Add description for MCP16502_REG_HPM to prevent a kernel-doc warning:
> 
> drivers/regulator/mcp16502.c:90: warning: Enum value 'MCP16502_REG_HPM' not described in enum 'mcp16502_reg'
> 
> 

Applied to

   broonie/regulator.git for-next

Thanks!

[1/1] regulator: mcp16502: add enum MCP16502_REG_HPM description
      commit: 84c13763f2a22acc31472dccde8b6130b8f2e9c2

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