linux-kernel - Re: [PATCH] MAINTAINERS: repair entry for MICROCHIP MCP16502 PMIC DRIVER

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: <170733006365.1096853.3231034830633743082.b4-ty@kernel.org>
Date: Wed, 07 Feb 2024 18:21:03 +0000
From: Mark Brown <broonie@...nel.org>
To: Andrei Simion <andrei.simion@...rochip.com>, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, 
 Claudiu Beznea <claudiu.beznea@...on.dev>, 
 Liam Girdwood <lgirdwood@...il.com>, linux-arm-kernel@...ts.infradead.org, 
 Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: repair entry for MICROCHIP MCP16502 PMIC
 DRIVER

On Wed, 07 Feb 2024 14:22:31 +0100, Lukas Bulwahn wrote:
> Commit 64db3e8d7be0 ("regulator: dt-bindings: microchip,mcp16502: convert
> to YAML") converts mcp16502-regulator.txt to microchip,mcp16502.yaml, but
> misses to adjust its reference in MAINTAINERS.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
> 
> [...]

Applied to

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

Thanks!

[1/1] MAINTAINERS: repair entry for MICROCHIP MCP16502 PMIC DRIVER
      commit: 46d5baf046abeffcb3754321fbc2551027fe7de9

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