From: Joe Perches <joe@perches.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Dmitri Belimov <d.belimov@gmail.com>,
Stefan Ringel <linuxtv@stefanringel.de>
Subject: Re: [PATCH 2/8] MAINTAINERS: tm6000: Update F: patterns
Date: Fri, 09 Dec 2011 07:49:50 -0800 [thread overview]
Message-ID: <1323445790.27746.10.camel@joe2Laptop> (raw)
In-Reply-To: <4EE1EC7F.4060909@redhat.com>
On Fri, 2011-12-09 at 09:09 -0200, Mauro Carvalho Chehab wrote:
> On 09-12-2011 06:12, Joe Perches wrote:
> > commit be30497085080 ("[media] move tm6000 to drivers/media/video")
> > move the files, update the F: pattern.
> > diff --git a/MAINTAINERS b/MAINTAINERS
[]
> > @@ -6375,11 +6375,6 @@ M: Omar Ramirez Luna<omar.ramirez@ti.com>
> > S: Odd Fixes
> > F: drivers/staging/tidspbridge/
> >
> > -STAGING - TRIDENT TVMASTER TMxxxx USB VIDEO CAPTURE DRIVERS
> > -L: linux-media@vger.kernel.org
> > -S: Odd Fixes
> > -F: drivers/staging/tm6000/
> > -
> > STAGING - USB ENE SM/MS CARD READER DRIVER
> > M: Al Cho<acho@novell.com>
> > S: Odd Fixes
> > @@ -6634,6 +6629,11 @@ F: include/linux/trace*.h
> > F: include/trace/
> > F: kernel/trace/
> >
> > +TRIDENT TVMASTER TMxxxx USB VIDEO CAPTURE DRIVERS
> > +L: linux-media@vger.kernel.org
> > +S: Odd Fixes
> > +F: drivers/media/video/tm6000/
> > +
[]
> I would either remove this entry or add a new one, cloning from the
> media entry, like:
>
> TRIDENT TVMASTER TMxxxx USB VIDEO CAPTURE DRIVERS
> M: Mauro Carvalho Chehab <mchehab@infradead.org>
> P: LinuxTV.org Project
> L: linux-media@vger.kernel.org
trivial: I think this "P:" line isn't really correct.
P: is meant for named individuals not collective projects.
> W: http://linuxtv.org
> Q: http://patchwork.kernel.org/project/linux-media/list/
> T: git git://linuxtv.org/media_tree.git
> S: Maintained
>
> If we add a new entry, it probably makes sense to add Stefan
> and/or Dmitri as co-maintainers there, if they're ok with that.
The more the merrier as far as I'm concerned.
Andrew, please ignore this one.
Mauro/Dmitri/Stefan, please submit whatever is appropriate.
next prev parent reply other threads:[~2011-12-09 15:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 8:12 [PATCH 0/8] MAINTAINERS: Update more " Joe Perches
2011-12-09 8:12 ` [PATCH 1/8] MAINTAINERS: staging: media: Update " Joe Perches
2011-12-09 10:58 ` Mauro Carvalho Chehab
2011-12-09 8:12 ` [PATCH 2/8] MAINTAINERS: tm6000: " Joe Perches
2011-12-09 11:09 ` Mauro Carvalho Chehab
2011-12-09 15:49 ` Joe Perches [this message]
2011-12-12 0:33 ` Dmitri Belimov
2011-12-09 8:12 ` [PATCH 3/8] MAINTAINERS: staging: tty: " Joe Perches
2011-12-09 8:12 ` [PATCH 4/8] MAINTAINERS: staging: westbridge: Delete section Joe Perches
2011-12-09 8:12 ` [PATCH 5/8] MAINTAINERS: serial:blackfin: Update F: pattern Joe Perches
2011-12-09 9:51 ` Zhang, Sonic
2011-12-09 8:12 ` [PATCH 6/8] MAINTAINERS: brcm80211: " Joe Perches
2011-12-09 9:17 ` Arend van Spriel
2011-12-09 8:12 ` [PATCH 7/8] MAINTAINERS: Delete generic_serial section Joe Perches
2011-12-09 8:12 ` [PATCH 8/8] MAINTAINERS: spi: Update F: patterns Joe Perches
2011-12-09 9:34 ` Wolfram Sang
2012-01-04 17:53 ` Grant Likely
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=1323445790.27746.10.camel@joe2Laptop \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=d.belimov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxtv@stefanringel.de \
--cc=mchehab@redhat.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