linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] MAINTAINERS: add keyword "tegra" to Tegra section
Date: Mon, 11 Feb 2013 10:30:28 -0800	[thread overview]
Message-ID: <1360607428.2028.37.camel@joe-AO722> (raw)
In-Reply-To: <1360606760.2028.34.camel@joe-AO722>

On Mon, 2013-02-11 at 10:19 -0800, Joe Perches wrote:
> On Mon, 2013-02-11 at 11:12 -0700, Stephen Warren wrote:
> > On 02/11/2013 11:04 AM, Joe Perches wrote:
> > > ./scripts/get_maintainer.pl -f arch/arm/mach-tegra
> > > wouldn't match anything.
> > 
> > That's annoying; it kinda defeats the whole purpose of this patch then.
> > 
> > The way this patch works out with a patch is because the file-names are
> > matched against the keywords since they appear in the patch. A solution
> > to the issue you raise would be to do the same in -f mode, by adding an
> > explicit pass to check the filenames that are found against MAINTAINERS
> > too. Do you have any objection to that?
> 
> Knock yourself out.
> 
> Are there any tegra related files that would not
> have tegra in the path?

To answer my own question:

$ git ls-files | grep -v tegra | xargs grep -Pl "(?i)[^a-z]tegra"
...

Several.  Most are Kconfig and Makefiles.
Most except staging/nvec don't seem to be very important.

      reply	other threads:[~2013-02-11 18:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 17:51 [PATCH V2] MAINTAINERS: add keyword "tegra" to Tegra section Stephen Warren
2013-02-11 17:56 ` Joe Perches
2013-02-11 18:01   ` Stephen Warren
2013-02-11 18:04     ` Joe Perches
2013-02-11 18:12       ` Stephen Warren
2013-02-11 18:19         ` Joe Perches
2013-02-11 18:30           ` Joe Perches [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=1360607428.2028.37.camel@joe-AO722 \
    --to=joe@perches.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).