[PATCH] MAINTAINERS: repair entry for MICROCHIP MCP16502 PMIC DRIVER

[PATCH] MAINTAINERS: repair entry for MICROCHIP MCP16502 PMIC DRIVER

[Lukas Bulwahn]

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.

Repair this file reference in MICROCHIP MCP16502 PMIC DRIVER.

Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
Mark, please pick this minor clean-up patch on top of the commit above.

 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index bb234d11f21e..e5087e4659f3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14415,7 +14415,7 @@ MICROCHIP MCP16502 PMIC DRIVER
 M:	Claudiu Beznea <claudiu.beznea@tuxon.dev>
 L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
 S:	Supported
-F:	Documentation/devicetree/bindings/regulator/mcp16502-regulator.txt
+F:	Documentation/devicetree/bindings/regulator/microchip,mcp16502.yaml
 F:	drivers/regulator/mcp16502.c
 
 MICROCHIP MCP3564 ADC DRIVER
-- 
2.17.1

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

[Mark Brown]

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