From: Stephen Warren <swarren@wwwdotorg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: arm@kernel.org, linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
Julian Andres Klode <jak@jak-linux.org>,
Marc Dietrich <marvin24@gmx.de>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH V4 2/2] MAINTAINERS: update Tegra section to capture all Tegra files
Date: Mon, 25 Feb 2013 13:56:53 -0700 [thread overview]
Message-ID: <512BD015.5000200@wwwdotorg.org> (raw)
In-Reply-To: <1360629574-23989-2-git-send-email-swarren@wwwdotorg.org>
On 02/11/2013 05:39 PM, 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.
Andrew, I see you've taken patch 1/2 into your tree. Are you planning on
taking patch 2/2 as well? Patch 2/2 depends on patch 1/2, so they really
should go through the same tree, or into different kernel versions or -rcs.
Thanks.
next prev parent reply other threads:[~2013-02-25 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 0:39 [PATCH V4 1/2] get_maintainer: allow keywords to match filenames Stephen Warren
2013-02-12 0:39 ` [PATCH V4 2/2] MAINTAINERS: update Tegra section to capture all Tegra files Stephen Warren
2013-02-25 20:56 ` Stephen Warren [this message]
2013-02-12 6:17 ` [PATCH V4 1/2] get_maintainer: allow keywords to match filenames Joe Perches
2013-02-12 18:17 ` Stephen Warren
2013-02-12 18:22 ` 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=512BD015.5000200@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=akpm@linux-foundation.org \
--cc=arm@kernel.org \
--cc=jak@jak-linux.org \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
--cc=swarren@nvidia.com \
/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