public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Joe Perches <joe@perches.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org,
	Sonic Zhang <sonic.adi@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: update maintainers for blackfin arch and drivers.
Date: Wed, 16 Nov 2011 13:35:54 -0500	[thread overview]
Message-ID: <201111161335.55744.vapier@gentoo.org> (raw)
In-Reply-To: <1321465409.16820.12.camel@Joe-Laptop>

[-- Attachment #1: Type: text/plain, Size: 2102 bytes --]

On Wednesday 16 November 2011 12:43:29 Joe Perches wrote:
> On Wed, 2011-11-16 at 12:11 -0500, Mike Frysinger wrote:
> > On Wednesday 16 November 2011 11:36:15 Joe Perches wrote:
> > > On Wed, 2011-11-16 at 10:20 -0500, Mike Frysinger wrote:
> > > > On Wednesday 16 November 2011 08:12:06 Joe Perches wrote:
> > > > > Drivers or arches without specific people to maintain
> > > > > them really should not have "S: Supported".
> > > > > These should really be "S: Orphan".
> > > > 
> > > > all the drivers are still maintained.  use the L: option to find the
> > > > maintainer.
> > > 
> > > I believe I know how the MAINTAINERS
> > > entries work.
> > > 
> > > From MAINTAINERS:
> > > 	M: Mail patches to: FullName <address@domain>
> > > 	L: Mailing list that is relevant to this area
> > > 
> > > Mailing lists aren't maintainers.
> > 
> > they contain all the maintainers
> 
> That's akin to lkml as the kernel maintainer.

no it isn't

> > > Maybe Analog Devices should create
> > > an email address alias like
> > > linux-devel@analog.com
> > 
> > so we should duplicate the ml into an alias to keep MAINTAINERS happy ?
> 
> When there is a company but not individuals responsible for
> an arch or drivers, then yes.

and that company already has a documented contact point.  have you found a 
time when a Blackfin question posted to the list wasn't answered ?  i doubt it.

> > makes no sense.  use the ml.
> 
> You mean the list that bounces my email?

your e-mail isn't bouncing.  i specifically configured things to silently 
moderate/accept e-mail from people.
	http://thread.gmane.org/gmane.linux.hardware.blackfin.kernel.devel/6125
(i'd show you this thread, but gmane has a bug when multiple lists are listed 
and things only get archived under one -- lkml in this case)

and i just checked the configuration.  your e-mail is explicitly listed under 
the accept_these_nonmembers field.

and i received your original replies via the blackfin ml.  i'm not subscribed 
to lkml, so there's no other way i could have seen your posts.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-11-16 18:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16  7:48 [PATCH] MAINTAINERS: update maintainers for blackfin arch and drivers Sonic Zhang
2011-11-16 13:12 ` Joe Perches
2011-11-16 15:20   ` [uclinux-dist-devel] " Mike Frysinger
2011-11-16 16:36     ` Joe Perches
2011-11-16 17:11       ` Mike Frysinger
2011-11-16 17:43         ` Joe Perches
2011-11-16 18:35           ` Mike Frysinger [this message]
2011-11-17  2:45   ` Zhang, Sonic
2011-11-18  8:36 ` [uclinux-dist-devel] " Barry Song

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=201111161335.55744.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sonic.adi@gmail.com \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    /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