From: Joe Perches <joe@perches.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
roel.kluin@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add hvc_console to MAINTAINERS
Date: Tue, 31 Mar 2009 14:10:23 -0700 [thread overview]
Message-ID: <1238533823.9715.292.camel@localhost> (raw)
In-Reply-To: <20090331132944.GB2332@yoda.jdub.homelinux.org>
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.
>
> Signed-off-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
> ---
>
> 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.
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
next prev parent reply other threads:[~2009-03-31 21:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49BF956B.9030109@gmail.com>
2009-03-30 20:35 ` [PATCH] hvc_console: prevent wrapping in hvc_console_print() 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 [this message]
2009-03-31 21:22 ` Andrew Morton
2009-03-31 21:40 ` Joe Perches
2009-03-31 23:52 ` Josh Boyer
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=1238533823.9715.292.camel@localhost \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=jwboyer@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).