From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Punit Agrawal <punit1.agrawal@toshiba.co.jp>,
Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
Anitha Chrisanthus <anitha.chrisanthus@intel.com>,
Wilken Gottwalt <wilken.gottwalt@posteo.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
John Stultz <john.stultz@linaro.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Yu Chen <chenyu56@huawei.com>, Sam Ravnborg <sam@ravnborg.org>,
Edmund Dea <edmund.j.dea@intel.com>,
kernel-janitors@vger.kernel.org, Joe Perches <joe@perches.com>,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH v5 4/4] MAINTAINERS: rectify entry for ALLWINNER HARDWARE SPINLOCK SUPPORT
Date: Tue, 26 Oct 2021 16:19:02 +0200 [thread overview]
Message-ID: <20211026141902.4865-5-lukas.bulwahn@gmail.com> (raw)
In-Reply-To: <20211026141902.4865-1-lukas.bulwahn@gmail.com>
Commit f9e784dcb63f ("dt-bindings: hwlock: add sun6i_hwspinlock") adds
Documentation/devicetree/bindings/hwlock/allwinner,sun6i-a31-hwspinlock.yaml,
but the related commit 3c881e05c814 ("hwspinlock: add sun6i hardware
spinlock support") adds a file reference to allwinner,sun6i-hwspinlock.yaml
instead.
Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
warning: no file matches F: Documentation/devicetree/bindings/hwlock/allwinner,sun6i-hwspinlock.yaml
Rectify this file reference in ALLWINNER HARDWARE SPINLOCK SUPPORT.
Reviewed-by: Wilken Gottwalt <wilken.gottwalt@posteo.net>
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 88cc726c36c0..aa88e9a0a747 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -761,7 +761,7 @@ F: drivers/crypto/allwinner/
ALLWINNER HARDWARE SPINLOCK SUPPORT
M: Wilken Gottwalt <wilken.gottwalt@posteo.net>
S: Maintained
-F: Documentation/devicetree/bindings/hwlock/allwinner,sun6i-hwspinlock.yaml
+F: Documentation/devicetree/bindings/hwlock/allwinner,sun6i-a31-hwspinlock.yaml
F: drivers/hwspinlock/sun6i_hwspinlock.c
ALLWINNER THERMAL DRIVER
--
2.26.2
prev parent reply other threads:[~2021-10-26 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 14:18 [PATCH v5 0/4] Rectify file references for dt-bindings in MAINTAINERS Lukas Bulwahn
2021-10-26 14:18 ` [PATCH v5 1/4] MAINTAINERS: rectify entry for ARM/TOSHIBA VISCONTI ARCHITECTURE Lukas Bulwahn
2021-10-26 14:19 ` [PATCH v5 2/4] MAINTAINERS: rectify entry for HIKEY960 ONBOARD USB GPIO HUB DRIVER Lukas Bulwahn
2021-10-26 14:19 ` [PATCH v5 3/4] MAINTAINERS: rectify entry for INTEL KEEM BAY DRM DRIVER Lukas Bulwahn
2021-10-26 14:19 ` Lukas Bulwahn [this message]
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=20211026141902.4865-5-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anitha.chrisanthus@intel.com \
--cc=chenyu56@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=edmund.j.dea@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=john.stultz@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mchehab+huawei@kernel.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=punit1.agrawal@toshiba.co.jp \
--cc=ralf.ramsauer@oth-regensburg.de \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=wilken.gottwalt@posteo.net \
/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).