From: robin.krahl@ireas.org (Robin Krahl)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Understanding get_maintainer.pl and MAINTAINERS
Date: Thu, 9 Mar 2017 20:03:14 +0100 [thread overview]
Message-ID: <20170309190314.GA23890@spectator> (raw)
In-Reply-To: <871su6vm81.fsf@miraculix.mork.no> <87d1dqvpdx.fsf@miraculix.mork.no>
Bj?rn, thanks for the explanations!
On 2017-03-09 09:13:46, Bj?rn Mork wrote:
> Yes, that looks like a bug in the MAINTAINERS entry. They probably
> intended something along
> N: bcm281.*
> N: bcm113.*
> N: bcm216.*
On 2017-03-09 10:22:06, Bj?rn Mork wrote:
> I am obviously not the first one making that bogus assumption. Very few
> of the "N:" entries in MAINTAINERS are anchored in any way. The rest of
> them are likely buggy. No one expects these strings to match in the
> middle of arbitrary path names. Even the example is a bit too wild
> IMHO:
>
> N: Files and directories with regex patterns.
> N: [^a-z]tegra all files whose path contains the word tegra
I?ll contact the maintainers for this particular entry. Should the
general issue be reported somewhere, e. g. on the LKML or to Joe Perches
as the get_maintainer.pl maintainer?
Robin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170309/95bc39fd/attachment.bin
prev parent reply other threads:[~2017-03-09 19:03 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
2017-03-09 9:22 ` Bjørn Mork
2017-03-09 19:03 ` Robin Krahl [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=20170309190314.GA23890@spectator \
--to=robin.krahl@ireas.org \
--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).