From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH] MAINTAINERS: repair reference in HYCON HY46XX TOUCHSCREEN SUPPORT
Date: Mon, 19 Apr 2021 08:00:23 +0200 [thread overview]
Message-ID: <20210419060023.3460-1-lukas.bulwahn@gmail.com> (raw)
Commit aa2f62cf211a ("Input: add driver for the Hycon HY46XX touchpanel
series") adds the file ./drivers/input/touchscreen/hycon-hy46xx.c, but the
file entry in MAINTAINERS refers to ./drivers/input/touchscreen/hy46xx.c.
Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
warning: no file matches F: drivers/input/touchscreen/hy46xx.c
Repair the file entry by referring to the right location.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
applies cleanly on next-20210419
Guilio, please ack.
Dmitry, please pick this minor clean up patch for your -next tree.
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index c54b8e4520d1..bbe356508f29 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8425,7 +8425,7 @@ M: Giulio Benetti <giulio.benetti@benettiengineering.com>
L: linux-input@vger.kernel.org
S: Maintained
F: Documentation/devicetree/bindings/input/touchscreen/hycon,hy46xx.yaml
-F: drivers/input/touchscreen/hy46xx.c
+F: drivers/input/touchscreen/hycon-hy46xx.c
HYGON PROCESSOR SUPPORT
M: Pu Wen <puwen@hygon.cn>
--
2.17.1
next reply other threads:[~2021-04-19 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 6:00 Lukas Bulwahn [this message]
2021-04-19 8:16 ` [PATCH] MAINTAINERS: repair reference in HYCON HY46XX TOUCHSCREEN SUPPORT Giulio Benetti
2021-04-21 5:40 ` Dmitry Torokhov
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=20210419060023.3460-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf.ramsauer@oth-regensburg.de \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).