public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan Wu <bryan.wu@analog.com>
To: Robin Getz <rgetz@blackfin.uclinux.org>
Cc: Mike Frysinger <vapier.adi@gmail.com>,
	Joe Perches <joe@perches.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Bad addresses in MAINTAINERS
Date: Tue, 14 Aug 2007 12:12:44 +0800	[thread overview]
Message-ID: <1187064764.21177.20.camel@roc-desktop> (raw)
In-Reply-To: <200708132354.22273.rgetz@blackfin.uclinux.org>

On Mon, 2007-08-13 at 23:54 -0400, Robin Getz wrote:
> On Mon 13 Aug 2007 15:56, Mike Frysinger pondered:
> > On 8/13/07, Joe Perches <joe@perches.com> wrote:
> > > On Mon, 2007-08-13 at 15:10 -0400, Mike Frysinger wrote:
> > > > On 8/13/07, Joe Perches <joe@perches.com> wrote:
> > > > > But if anyone has a new email address and still wants
> > > > > to be in the maintainers file, please send.
> > > > >
> > > > > BLACKFIN ARCHITECTURE
> > > > > P:      Aubrey Li
> > > > > M:      aubrey.li@analog.com
> > > > > P:      Jerry Zeng
> > > > > M:      jerry.zeng@analog.com
> > > >
> > > > we know these guys needed to be removed as they've recently left ADI,
> > > > we just havent pushed to mainline
> > >
> > > Maybe you can have a "blackfin_arch@analog.com" list as maintainers?
> > 
> > we have a mailing list already ... could just drop the general list of
> > people for Blackfin and keep specific e-mails for specific drivers
> 
> There is a public mailing list - but it is closed - must be subscribed to post  
> (cuts down on spam), and I thought the requirement was to have these be open 
> lists?

Yes, open a public mailing list is a good choice to replace the whole
team member list.

How about some driver code maintainers?

- Bryan

> -
> 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/

  parent reply	other threads:[~2007-08-14  4:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13 19:07 Bad addresses in MAINTAINERS Joe Perches
2007-08-13 19:10 ` Mike Frysinger
2007-08-13 19:19   ` Joe Perches
2007-08-13 19:56     ` Mike Frysinger
2007-08-14  3:54       ` Robin Getz
2007-08-14  4:11         ` Mike Frysinger
2007-08-14  4:12         ` Bryan Wu [this message]
2007-08-14  4:17           ` Joe Perches
2007-08-14  4:58           ` Mike Frysinger
2007-08-14  9:59         ` Alan Cox
2007-08-14 13:09           ` Mike Frysinger
2007-08-13 19:24 ` Adrian Bunk
2007-08-13 19:42   ` Joe Perches
2007-08-14  4:18   ` Len Brown
2007-08-13 20:27 ` Antonino A. Daplas
2007-08-14  2:21   ` Paul Mundt
2007-08-14  2:46     ` Joe Perches
2007-08-14 13:13       ` Adrian Bunk
2007-08-13 20:56 ` Alan Cox
2007-08-14 12:09 ` Maciej W. Rozycki

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=1187064764.21177.20.camel@roc-desktop \
    --to=bryan.wu@analog.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=vapier.adi@gmail.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