From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: fix bad sdei paths
Date: Fri, 5 Oct 2018 15:21:20 +0100 [thread overview]
Message-ID: <20181005142120.13279-1-james.morse@arm.com> (raw)
The SDEI header files had an 'arm_' namespace added, but the patterns
in the MAINTAINERS files were missed. Oops.
Reported-by: Joe Perches <joe@perches.com>
Signed-off-by: James Morse <james.morse@arm.com>
---
The SDEI stuff originally went via arm64, ... what about this?
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2c7069037a15..30df8d42baa9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -13186,8 +13186,8 @@ L: linux-arm-kernel at lists.infradead.org
S: Maintained
F: Documentation/devicetree/bindings/arm/firmware/sdei.txt
F: drivers/firmware/arm_sdei.c
-F: include/linux/sdei.h
-F: include/uapi/linux/sdei.h
+F: include/linux/arm_sdei.h
+F: include/uapi/linux/arm_sdei.h
SOFTWARE RAID (Multiple Disks) SUPPORT
M: Shaohua Li <shli@kernel.org>
--
2.17.1
next reply other threads:[~2018-10-05 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 14:21 James Morse [this message]
2018-10-05 16:55 ` [PATCH] MAINTAINERS: fix bad sdei paths Catalin Marinas
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=20181005142120.13279-1-james.morse@arm.com \
--to=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.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