From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Change BCMRING maintainer
Date: Wed, 16 Jun 2010 10:58:23 +0800 [thread overview]
Message-ID: <AANLkTilI2toj42vZcHzPC4ru82CDMf2UWsTasPyOD3Nh@mail.gmail.com> (raw)
In-Reply-To: <1276655981.1586.172.camel@Joe-Laptop.home>
On Wed, Jun 16, 2010 at 10:39 AM, Joe Perches <joe@perches.com> wrote:
> On Wed, 2010-06-16 at 10:17 +0800, Eric Miao wrote:
>> On Wed, Jun 16, 2010 at 4:42 AM, JD (Jiandong) Zheng
>> <jdzheng@broadcom.com> wrote:
>> > I am Jiandong Zheng working on BCMRING in Broadcom Canada Ltd.
>> > I am replacing Leo Chen (leochen at broadcom.com) as
>> > "ARM/BCMRING ARM ARCHITECTURE" and "ARM/BCMRING MTD NAND DRIVER"
>> > ?maintainer.
>> > Signed-off-by: Jiandong Zheng <jdzheng@broadcom.com>
>> Search your email address in linux-2.6 tree, no result found. This is
>> community, not a company. Maintainer is not assigned. Show us some
>> credits please?
>
> I think you're going overboard Eric.
> You'll find several company addresses, some with names, in MAINTAINERS.
Well, I'm not against a company address at all, I myself am employed and
use company address very often. And I really welcome some one to come up
and take the responsibility of some orphaned code. But the first impression
of this, to me, it's more like a Broadcom internal policy to assign someone
or not (maybe some work transition of Leo Chen). And I haven't seen much
contribution from JD so far, honestly, (but doesn't mean I don't believe
he's going to contribute a lot).
Sorry, JD, I was a bit rude on this and this is not personal at all. Nice to
know you actually, bcmring was not actively maintained since last year.
I hope we can know more about you.
>
> for instance:
> $ grep M:.*support MAINTAINERS
> M: ? ? ?support at lsi.com
> M: ? ? ?Vincent Sanders <support@simtec.co.uk>
> M: ? ? ?Vincent Sanders <support@simtec.co.uk>
> M: ? ? ?Matthias Bruestle and Harald Welte <support@reiner-sct.com>
> M: ? ? ?Support Department <support@connecttech.com>
>
> Some others:
> M: ? ? ?STEricsson <STEricsson_nomadik_linux@list.st.com>
> M: ? ? ?"Digi International, Inc" <Eng.Linux@digi.com>
> M: ? ? ?HighPoint Linux Team <linux@highpoint-tech.com>
> M: ? ? ?Intel Linux Wireless <ilw@linux.intel.com>
> M: ? ? ?linux-wimax at intel.com
> M: ? ? ?linux390 at de.ibm.com
> M: ? ? ?linux-driver at qlogic.com
> M: ? ? ?Solarflare linux maintainers <linux-net-drivers@solarflare.com>
> M: ? ? ?davinci-linux-open-source at linux.davincidsp.com
>
> Would you prefer that broadcom go the way of intel with the
> ipw2x00 or just have a faceless "linux-support at broadcom.com"?
>
> Not me.
>
> Welcome JD.
>
>
>
next prev parent reply other threads:[~2010-06-16 2:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 20:42 [PATCH] MAINTAINERS: Change BCMRING maintainer JD (Jiandong) Zheng
2010-06-16 2:17 ` Eric Miao
2010-06-16 2:39 ` Joe Perches
2010-06-16 2:58 ` Eric Miao [this message]
2010-06-16 16:49 ` JD (Jiandong) Zheng
2010-06-17 3:18 ` Eric Miao
2010-06-17 17:14 ` JD (Jiandong) Zheng
2010-06-17 18:40 ` Russell King - ARM Linux
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=AANLkTilI2toj42vZcHzPC4ru82CDMf2UWsTasPyOD3Nh@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).