From: Stephen Warren <swarren@wwwdotorg.org>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Stephen Warren <swarren@nvidia.com>,
Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>, Lucas Stach <dev@lynxeye.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
nouveau@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@canonical.com>
Subject: Re: nouveau lockdep splat
Date: Wed, 06 Mar 2013 12:31:49 -0700 [thread overview]
Message-ID: <513799A5.3010609@wwwdotorg.org> (raw)
In-Reply-To: <20130306191418.GA3400@joi.lan>
On 03/06/2013 12:14 PM, Marcin Slusarz wrote:
> On Wed, Mar 06, 2013 at 01:04:29AM +0100, Borislav Petkov wrote:
>> On Tue, Mar 05, 2013 at 05:30:52PM +0100, Lucas Stach wrote:
>>> Dropping Tegra ML, it's not the place where Nouveau mails should go.
>>
>> $ ./scripts/get_maintainer.pl -f drivers/gpu/drm/nouveau/nv50_display.c
>> ...
>> linux-tegra@vger.kernel.org (open list:TEGRA SUPPORT)
>>
>> Maybe get_maintainer.pl patterns need correction...
>
> That's new feature (introduced in commit eb90d0855b75f8 "get_maintainer: allow
> keywords to match filenames") of get_maintainer.pl which now can look at file
> contents...
get_maintainer.pl could always look at file contents IIRC. The change
was that I added keyword "tegra" to the Tegra section that now matches
this file's contents.
./scripts/get_maintainer.pl -f drivers/gpu/drm/nouveau
... might be a better invocation, although perhaps I should add an
explicit exclusion for "nouveau" to the Tegra section in MAINTAINERS.
next prev parent reply other threads:[~2013-03-06 19:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 21:16 Borislav Petkov
2013-03-05 16:30 ` Lucas Stach
2013-03-06 0:04 ` Borislav Petkov
2013-03-06 19:14 ` Marcin Slusarz
2013-03-06 19:31 ` Stephen Warren [this message]
2013-03-06 19:53 ` Borislav Petkov
2013-03-06 20:02 ` Joe Perches
2013-03-06 19:42 ` Borislav Petkov
2013-03-19 20:24 ` Borislav Petkov
2013-03-19 20:40 ` [Nouveau] " Peter Hurley
2013-03-20 6:35 ` Lijo Antony
2013-03-20 15:23 ` Lijo Antony
2013-03-20 15:29 ` Borislav Petkov
2013-03-24 18:00 ` Lijo Antony
2013-03-24 19:49 ` Borislav Petkov
2013-03-07 11:20 ` Arend van Spriel
2013-03-11 14:20 ` Arend van Spriel
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=513799A5.3010609@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dev@lynxeye.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=marcin.slusarz@gmail.com \
--cc=nouveau@lists.freedesktop.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
Powered by JetHome