From: jon.mason@broadcom.com (Jon Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] MAINTAINERS: Update BCM63XX entry
Date: Mon, 20 Jun 2016 17:07:36 -0400 [thread overview]
Message-ID: <1466456857-11969-4-git-send-email-jon.mason@broadcom.com> (raw)
In-Reply-To: <1466456857-11969-1-git-send-email-jon.mason@broadcom.com>
There are more files being supported by the BCM63XX than simply
"arch/arm/mach-bcm/bcm63xx.c" and "arch/arm/include/debug/bcm63xx.S".
Add a regex of "bcm63xx" to catch all the other files that are out
there.
Signed-off-by: Jon Mason <jon.mason@broadcom.com>
---
MAINTAINERS | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 81be402..28a35f4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2523,8 +2523,7 @@ L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
L: bcm-kernel-feedback-list at broadcom.com
T: git git://github.com/broadcom/stblinux.git
S: Maintained
-F: arch/arm/mach-bcm/bcm63xx.c
-F: arch/arm/include/debug/bcm63xx.S
+N: bcm63xx
BROADCOM BCM63XX/BCM33XX UDC DRIVER
M: Kevin Cernekee <cernekee@gmail.com>
--
1.9.1
next prev parent reply other threads:[~2016-06-20 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 21:07 [PATCH 0/4] MAINTAINERS: update BCM SoC entries Jon Mason
2016-06-20 21:07 ` [PATCH 1/4] MAINTAINERS: Fix nsp false-positives Jon Mason
2016-06-20 21:07 ` [PATCH 2/4] MAINTAINERS: Add NS2 entry Jon Mason
2016-06-20 21:07 ` Jon Mason [this message]
2016-06-20 21:07 ` [PATCH 4/4] MAINTAINERS: Update BCM281XX/BCM11XXX/BCM216XX entry Jon Mason
2016-06-20 21:35 ` Chris Brand
2016-06-21 14:34 ` Jon Mason
2016-06-21 16:07 ` Chris Brand
2016-06-23 2:54 ` Florian Fainelli
2016-06-20 21:14 ` [PATCH 0/4] MAINTAINERS: update BCM SoC entries Scott Branden
2016-07-05 23:27 ` Florian Fainelli
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=1466456857-11969-4-git-send-email-jon.mason@broadcom.com \
--to=jon.mason@broadcom.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;
as well as URLs for NNTP newsgroup(s).