From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Emil Renner Berthing <kernel@esmil.dk>,
Jianlong Huang <jianlong.huang@starfivetech.com>,
Hal Feng <hal.feng@linux.starfivetech.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH] MAINTAINERS: adjust STARFIVE JH7100 PINCTRL DRIVER after file movement
Date: Thu, 6 Oct 2022 10:01:54 +0200 [thread overview]
Message-ID: <20221006080154.5396-1-lukas.bulwahn@gmail.com> (raw)
Commit ba7fdf88e98a ("pinctrl: Create subdirectory for StarFive drivers")
moves pinctrl-starfive.c into its own subdirectory starfive; further,
commit ba99b756da17 ("pinctrl: starfive: Rename "pinctrl-starfive" to
"pinctrl-starfive-jh7100"") adds the suffix jh7100 to the driver and
dt-bindings header file name.
These commits however do not adjust the entry in MAINTAINERS. Hence,
./scripts/get_maintainer.pl --self-test=patterns complains about a broken
reference.
Adjust the entries for STARFIVE JH7100 PINCTRL DRIVER after file movement.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2a1347b5fd07..37a9f9e7f6c8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19603,8 +19603,8 @@ M: Emil Renner Berthing <kernel@esmil.dk>
L: linux-gpio@vger.kernel.org
S: Maintained
F: Documentation/devicetree/bindings/pinctrl/starfive,jh7100-pinctrl.yaml
-F: drivers/pinctrl/pinctrl-starfive.c
-F: include/dt-bindings/pinctrl/pinctrl-starfive.h
+F: drivers/pinctrl/starfive/
+F: include/dt-bindings/pinctrl/pinctrl-starfive-jh7100.h
STARFIVE JH7100 RESET CONTROLLER DRIVER
M: Emil Renner Berthing <kernel@esmil.dk>
--
2.17.1
next reply other threads:[~2022-10-06 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 8:01 Lukas Bulwahn [this message]
2022-10-06 8:07 ` [PATCH] MAINTAINERS: adjust STARFIVE JH7100 PINCTRL DRIVER after file movement Emil Renner Berthing
2022-10-06 9:23 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221006080154.5396-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=hal.feng@linux.starfivetech.com \
--cc=jianlong.huang@starfivetech.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@esmil.dk \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox