[PATCH] MAINTAINERS: repair file entry in CHROMEOS EC HARDWARE MONITORING

[PATCH] MAINTAINERS: repair file entry in CHROMEOS EC HARDWARE MONITORING

[Lukas Bulwahn]

From: Lukas Bulwahn <lukas.bulwahn@redhat.com>

Commit e8665a172378 ("hwmon: add ChromeOS EC driver") adds a driver, some
documentation and the new section CHROMEOS EC HARDWARE MONITORING in
MAINTAINERS. The commit adds Documentation/hwmon/cros_ec_hwmon.rst. The
file entry in the MAINTAINERS section however accidentally refers to
chros_ec_hwmon.rst.

Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
broken reference.

Refer to the intended documentation file.

Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
---
 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 3eab6c381a3b..09813e21da27 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5143,7 +5143,7 @@ M:	Thomas Weißschuh <thomas@weissschuh.net>
 L:	chrome-platform@lists.linux.dev
 L:	linux-hwmon@vger.kernel.org
 S:	Maintained
-F:	Documentation/hwmon/chros_ec_hwmon.rst
+F:	Documentation/hwmon/cros_ec_hwmon.rst
 F:	drivers/hwmon/cros_ec_hwmon.c
 
 CHROMEOS EC SUBDRIVERS
-- 
2.45.1

Re: [PATCH] MAINTAINERS: repair file entry in CHROMEOS EC HARDWARE MONITORING

[Tzung-Bi Shih]

On Mon, Jun 03, 2024 at 09:23:43AM +0200, Lukas Bulwahn wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> 
> Commit e8665a172378 ("hwmon: add ChromeOS EC driver") adds a driver, some
> documentation and the new section CHROMEOS EC HARDWARE MONITORING in
> MAINTAINERS. The commit adds Documentation/hwmon/cros_ec_hwmon.rst. The
> file entry in the MAINTAINERS section however accidentally refers to
> chros_ec_hwmon.rst.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
> 
> Refer to the intended documentation file.

Thanks for your patch.

Received a notification about the error in [1] earlier.  Given that it is a
minor issue, I fixed it directly to the original commit (instead of sending
out an independent patch with Fixes tag).  It should be fixed in the following
linux-next (e.g. next-20240604).

[1]: https://lore.kernel.org/linux-next/20240603132517.7f344f9f@canb.auug.org.au/