From: chris.brand@broadcom.com (Chris Brand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] MAINTAINERS: Update BCM281XX/BCM11XXX/BCM216XX entry
Date: Mon, 20 Jun 2016 14:35:07 -0700 [thread overview]
Message-ID: <CAMsMSK-7WOuzVNASmLdAsm8PzRARJCZB5zVReZmfZPCYLtg=HQ@mail.gmail.com> (raw)
In-Reply-To: <1466456857-11969-5-git-send-email-jon.mason@broadcom.com>
On Mon, Jun 20, 2016 at 2:07 PM, Jon Mason <jon.mason@broadcom.com> wrote:
> There are many clock, pinctl, and misc others that should be covered
> under the BCM281XX/BCM11XXX/BCM216XX ARM listing. Change the entry to
> use regex's that should cover all the files.
>
> Also, remove the bcm_defconfig entry (as the file is being removed), and
> arch/arm64/boot/dts/broadcom reference (as that is not accurate for this
> group of maintainers and all the device trees under it should now be
> covered by other maintainer entries).
>
> Signed-off-by: Jon Mason <jon.mason@broadcom.com>
> ---
> MAINTAINERS | 11 ++++-------
> 1 file changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 28a35f4..01382ce 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2481,14 +2481,11 @@ M: Scott Branden <sbranden@broadcom.com>
> L: bcm-kernel-feedback-list at broadcom.com
> T: git git://github.com/broadcom/mach-bcm
> S: Maintained
> +N: bcm281*
> +N: bcm113*
> +N: bcm216*
> +N: kona
Hmmm. We should probably add bcm23550 here, too.
> F: arch/arm/mach-bcm/
> -F: arch/arm/boot/dts/bcm113*
> -F: arch/arm/boot/dts/bcm216*
> -F: arch/arm/boot/dts/bcm281*
> -F: arch/arm64/boot/dts/broadcom/
> -F: arch/arm/configs/bcm_defconfig
> -F: drivers/mmc/host/sdhci-bcm-kona.c
> -F: drivers/clocksource/bcm_kona_timer.c
>
> BROADCOM BCM2835 ARM ARCHITECTURE
> M: Stephen Warren <swarren@wwwdotorg.org>
Chris
next prev parent reply other threads:[~2016-06-20 21:35 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 ` [PATCH 3/4] MAINTAINERS: Update BCM63XX entry Jon Mason
2016-06-20 21:07 ` [PATCH 4/4] MAINTAINERS: Update BCM281XX/BCM11XXX/BCM216XX entry Jon Mason
2016-06-20 21:35 ` Chris Brand [this message]
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='CAMsMSK-7WOuzVNASmLdAsm8PzRARJCZB5zVReZmfZPCYLtg=HQ@mail.gmail.com' \
--to=chris.brand@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).