From: bjorn@mork.no (Bjørn Mork)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Understanding get_maintainer.pl and MAINTAINERS
Date: Thu, 09 Mar 2017 09:13:46 +0100 [thread overview]
Message-ID: <87d1dqvpdx.fsf@miraculix.mork.no> (raw)
In-Reply-To: <20170308230857.GA14605@nohappyview.fritz.box> (Robin Krahl's message of "Thu, 9 Mar 2017 00:08:57 +0100")
Robin Krahl <robin.krahl@ireas.org> writes:
> Hi again,
>
> I?m now preparing my patchset for bcm2835-audio. get_maintainer.pl
> returns:
>
> $ ./scripts/get_maintainer.pl --nokeywords --nogit --nogit-fallback drivers/staging/vc04_services/bcm2835-audio/
> Stephen Warren <swarren@wwwdotorg.org> (maintainer:BROADCOM BCM2835 ARM ARCHITECTURE)
> Lee Jones <lee@kernel.org> (maintainer:BROADCOM BCM2835 ARM ARCHITECTURE)
> Eric Anholt <eric@anholt.net> (maintainer:BROADCOM BCM2835 ARM ARCHITECTURE)
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:STAGING SUBSYSTEM)
> Florian Fainelli <f.fainelli@gmail.com> (maintainer:BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE...)
> Ray Jui <rjui@broadcom.com> (maintainer:BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE...)
> Scott Branden <sbranden@broadcom.com> (maintainer:BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE...)
> bcm-kernel-feedback-list at broadcom.com (maintainer:BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE...)
> linux-rpi-kernel at lists.infradead.org (moderated list:BROADCOM BCM2835 ARM ARCHITECTURE)
> linux-arm-kernel at lists.infradead.org (moderated list:BROADCOM BCM2835 ARM ARCHITECTURE)
> devel at driverdev.osuosl.org (open list:STAGING SUBSYSTEM)
> linux-kernel at vger.kernel.org (open list)
>
> Why are the BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE guys added
> to the list? The MAINTAINERS file defines these rules:
>
> BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITECTURE
> M: Florian Fainelli <f.fainelli@gmail.com>
> M: Ray Jui <rjui@broadcom.com>
> M: Scott Branden <sbranden@broadcom.com>
> M: 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
> F: arch/arm/mach-bcm/
>
> As far as I see, none of these rules matches the given path. Am I
> missing something?
The N entries are regex patterns. "bcm281*" matches any name starting
with "bcm28", followed by 0 or more 1's. So "bcm2835-audio" matches.
Yes, that looks like a bug in the MAINTAINERS entry. They probably
intended something along
N: bcm281.*
N: bcm113.*
N: bcm216.*
Bj?rn
next prev parent reply other threads:[~2017-03-09 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 23:08 Understanding get_maintainer.pl and MAINTAINERS Robin Krahl
2017-03-09 8:13 ` Bjørn Mork [this message]
2017-03-09 9:22 ` Bjørn Mork
2017-03-09 19:03 ` Robin Krahl
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=87d1dqvpdx.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=kernelnewbies@lists.kernelnewbies.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).