Re: [PATCH] [472/2many] MAINTAINERS - TI OMAP MMC INTERFACE DRIVER

["Satyam Sharma" <satyam.sharma@gmail.com>]

On 8/13/07, Satyam Sharma <satyam.sharma@gmail.com> wrote:
> On 8/13/07, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > On Sun, 12 Aug 2007 23:37:08 -0700
> > joe@perches.com wrote:
> >
> > > Add file pattern to MAINTAINER entry
> > >
> > > Signed-off-by: Joe Perches <joe@perches.com>
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index af16a17..7a7f837 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -4478,7 +4478,7 @@ F:      drivers/misc/tifm*
> > >  F:   drivers/mmc/host/tifm_sd.c
> > >
> > >  TI OMAP MMC INTERFACE DRIVER
> > > -P:   Carlos Aguiar, Anderson Briglia and Syed Khasim
> > > +P:   Carlos Aguiar - Anderson Briglia - Syed Khasim
> >
> > NAK, Please stop sneaking other irrelevant changes into the patchset
>
> Joe, it's okay to have multiple "P:" entries for the same driver/subsystem
> in MAINTAINERS (grep BLACKFIN ARCHITECTURE for an extreme example :-)
> So you could probably do something like that here as well (but continue
> to have a single "M:" entry),

Well, three maintainers listed for this driver, but the only email address
they want to give out there is:

linux-omap-open-source@linux.omap.com

which leads to:

"You are not allowed to post to this mailing list, and your message has
been automatically rejected.  If you think that your messages are
being rejected in error, contact the mailing list owner at
linux-omap-open-source-owner@linux.omap.com."

I think the real "bad patch" that should've been "NAK"ed here was the
original patch to MAINTAINERS itself that introduced this entry.


> though as Alan mentions it isn't really good
> to make different kind of changes in the same patch.
>
> BTW bad, sad, things happened to my mailbox while I was away :-(
>
> Satyam
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/