From: Stephen Warren <swarren@wwwdotorg.org>
To: Joe Perches <joe@perches.com>
Cc: arm@kernel.org, linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH V2] MAINTAINERS: add keyword "tegra" to Tegra section
Date: Mon, 11 Feb 2013 11:01:12 -0700 [thread overview]
Message-ID: <511931E8.3080802@wwwdotorg.org> (raw)
In-Reply-To: <1360605395.2028.28.camel@joe-AO722>
On 02/11/2013 10:56 AM, Joe Perches wrote:
> On Mon, 2013-02-11 at 10:51 -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.
>>
>> Cc: Joe Perches <joe@perches.com>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>> MAINTAINERS | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index b98c89b..10e9b31 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -7829,9 +7829,7 @@ L: linux-tegra@vger.kernel.org
>> Q: http://patchwork.ozlabs.org/project/linux-tegra/list/
>> T: git git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git
>> S: Supported
>> -F: arch/arm/mach-tegra
>> -F: arch/arm/boot/dts/tegra*
>> -F: arch/arm/configs/tegra_defconfig
>> +K: (?i)[^a-z]tegra
>>
>> TEHUTI ETHERNET DRIVER
>> M: Andy Gospodarek <andy@greyhouse.net>
>
> It's probably not a good idea to remove
> any of the F: lines as there are files
> that could get modified in those paths
> without any tegra word in the patch.
At least for those F: lines that exist already and are removed above,
the keyword will match their filename, so there's no issue here.
next prev parent reply other threads:[~2013-02-11 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 17:51 Stephen Warren
2013-02-11 17:56 ` Joe Perches
2013-02-11 18:01 ` Stephen Warren [this message]
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
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=511931E8.3080802@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arm@kernel.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=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
all inboxes | Powered by JetHome®