From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@ozlabs.org, roel.kluin@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add hvc_console to MAINTAINERS
Date: Tue, 31 Mar 2009 19:52:48 -0400 [thread overview]
Message-ID: <20090331235248.GC563@zod.rchland.ibm.com> (raw)
In-Reply-To: <1238535658.9715.321.camel@localhost>
On Tue, Mar 31, 2009 at 02:40:58PM -0700, Joe Perches wrote:
>On Tue, 2009-03-31 at 14:22 -0700, Andrew Morton wrote:
>> On Tue, 31 Mar 2009 14:10:23 -0700
>> Joe Perches <joe@perches.com> wrote:
>> > On Tue, 2009-03-31 at 09:29 -0400, Josh Boyer wrote:
>> > > Add a MAINTAINERS entry for the hypervisor virtual console support
>> > > used on IBM POWER servers.
>> > > diff --git a/MAINTAINERS b/MAINTAINERS
>> > > index c5f4e9d..387ad45 100644
>> > > --- a/MAINTAINERS
>> > > +++ b/MAINTAINERS
>> > > @@ -2176,6 +2176,11 @@ W: http://www.ia64-linux.org/
>> > > T: git kernel.org:/pub/scm/linux/kernel/git/aegl/linux-2.6.git
>> > > S: Maintained
>> > >
>> > > +IBM HYPERVISOR VIRTUAL CONSOLE
>> > > +P: Several
>> > > +L: linuxppc-dev@ozlabs.org
>> > > +S: Maintained
>> > > +
>> > > IBM MCA SCSI SUBSYSTEM DRIVER
>> > > P: Michael Lang
>> > > M: langa2@kph.uni-mainz.de
>> >
>> > I think this sort of entry should not be acceptable.
>> > Maintainers should have individual names and contact addresses.
>>
>> There isn't a maintainer.
>>
>> But people send patches to the wrong list, so the ppc guys (who use
>> this driver) don't get to see them.
>>
>> That's a practical, real-world problem. We should have a fix for it.
>>
>> > An exploder entry should be OK though.
>> > For instance, the DVB subsystem:
>> >
>> > DVB SUBSYSTEM AND DRIVERS
>> > P: LinuxTV.org Project
>> > M: linux-media@vger.kernel.org
>> >
>> > A list entry could be something like:
>> >
>> > P: Linux PCMCIA Team
>> > L: linux-pcmcia@lists.infradead.org
>> >
>>
>> I'm unclear on what the difference is here..
>
>I have no problem with the "L: list" entry.
>I think that's good. Along with some file
>matching pattern as well of course...
>
>I think the "P: Several" entry is not good.
>
>"Several" doesn't give any idea as to who
>actually does the work.
I copied that from something else in MAINTAINERS. I believe it
was the KERNEL JANITORS entry. I guess I should have known better
than to copy from that...
>If the "P:" entry is there at all, it should
>be the list name.
>
>Maybe "P: Linux PPC Development Team" or
>something similar.
Except that isn't right for the reasons Michael specified.
josh
next prev parent reply other threads:[~2009-03-31 23:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 12:19 [PATCH] hvc_console: prevent wrapping in hvc_console_print() Roel Kluin
2009-03-30 20:35 ` Andrew Morton
2009-03-30 20:55 ` Josh Boyer
2009-03-30 21:18 ` Andrew Morton
2009-03-31 13:29 ` [PATCH] Add hvc_console to MAINTAINERS Josh Boyer
2009-03-31 21:10 ` Joe Perches
2009-03-31 21:22 ` Andrew Morton
2009-03-31 21:40 ` Joe Perches
2009-03-31 23:52 ` Josh Boyer [this message]
2009-03-31 23:44 ` Michael Ellerman
2009-03-31 23:50 ` Josh Boyer
2009-04-01 0:04 ` Michael Ellerman
2009-04-01 0:20 ` Michael Ellerman
2009-04-01 0:33 ` Josh Boyer
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=20090331235248.GC563@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=roel.kluin@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
all inboxes | Powered by JetHome®