From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 2/2] MAINTAINERS: update Tegra section to capture all Tegra files
Date: Mon, 11 Feb 2013 16:02:48 -0800 [thread overview]
Message-ID: <1360627368.4707.8.camel@joe-AO722> (raw)
In-Reply-To: <1360626016-23332-2-git-send-email-swarren@wwwdotorg.org>
On Mon, 2013-02-11 at 16:40 -0700, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> The intent is to ensure that all Tegra-related patches are sent to the
> linux-tegra@ mailing list, so people can keep up-to-date on all misc
> driver changes.
>
> Doing this with a keyword is far simpler and more compact than listing
> all Tegra-related drivers, even if wildcards were used.
>
> Words such as integrate or integrator are common. Ensure the character
> right before "tegra" isn't a-z (case-insensitive), to make sure the
> keyword doesn't match those.
>
> The only files that the keyword doesn't match are the NVEC driver. Add
> the linux-tegra mailing list to the NVEC entry to solve this.
You should probably add some commentary/documentation
to the K: section description of MAINTAINERS in patch 1/2.
Something about K: patterns also matching filenames.
K: Keyword perl extended regex pattern to match content in a
patch or file. For instance:
K: of_get_profile
matches patches or files that contain "of_get_profile"
K: \b(printk|pr_(info|err))\b
matches patches or files that contain one or more of the words
printk, pr_info or pr_err
One regex pattern per line. Multiple K: lines acceptable.
next prev parent reply other threads:[~2013-02-12 0:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 23:40 [PATCH V3 1/2] get_maintainer: allow keywords to match filenames Stephen Warren
2013-02-11 23:40 ` [PATCH V3 2/2] MAINTAINERS: update Tegra section to capture all Tegra files Stephen Warren
2013-02-12 0:02 ` Joe Perches [this message]
2013-02-12 0:00 ` [PATCH V3 1/2] get_maintainer: allow keywords to match filenames Joe Perches
2013-02-12 0:08 ` Stephen Warren
2013-02-12 0:16 ` Joe Perches
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=1360627368.4707.8.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).