From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: Dmitry Torokhov <dtor@vmware.com>,
linux-kernel@vger.kernel.org, pv-drivers@vmware.com
Subject: Re: [PATCH] MAINTAINERS: add entry for VMware Balloon driver
Date: Wed, 18 Jun 2014 16:49:34 -0700 [thread overview]
Message-ID: <20140618234934.GA9378@kroah.com> (raw)
In-Reply-To: <1403134100.14018.8.camel@joe-AO725>
On Wed, Jun 18, 2014 at 04:28:20PM -0700, Joe Perches wrote:
> On Wed, 2014-06-18 at 16:19 -0700, Dmitry Torokhov wrote:
> > On Wednesday, June 18, 2014 04:17:42 PM Greg Kroah-Hartman wrote:
> > > On Wed, Jun 18, 2014 at 04:09:01PM -0700, Dmitry Torokhov wrote:
> > > > Signed-off-by: Dmitry Torokhov <dtor@vmware.com>
> > > > ---
> > > >
> > > > MAINTAINERS | 6 ++++++
> > > > drivers/misc/vmw_balloon.c | 2 +-
> > > > 2 files changed, 7 insertions(+), 1 deletions(-)
> > > >
> > > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > > index 6c484ac..3a446e8 100644
> > > > --- a/MAINTAINERS
> > > > +++ b/MAINTAINERS
> > > > @@ -9645,6 +9645,12 @@ L: virtualization@lists.linux-foundation.org
> > > >
> > > > S: Supported
> > > > F: arch/x86/kernel/cpu/vmware.c
> > > >
> > > > +VMWARE BALLOON DRIVER
> > > > +M: "VMware, Inc." <pv-drivers@vmware.com>
> > > > +L: linux-kernel@vger.kernel.org
> > > > +S: Maintained
> > > > +F: drivers/misc/vmw_balloon.c
> > >
> > > I really hate having a "alias" as a maintainer, and not a "real" name.
> > > Kernel development is done by individuals, we don't have companies as
> > > authors or signed-off-by lines, we have developers.
> > >
> > > So I will not accept this, sorry. Please find a real person who is
> > > willing to maintain this code, or just mark it unsupported.
> > >
> >
> > OK, fair enough, we'll find a real name to attach here.
>
> It's definitely better to have a person's name there but
> there are many company exploders/aliases in MAINTAINERS.
>
> There already is a pv-drivers@vmware.com too.
>
> MAINTAINERS:M: Adaptec OEM Raid Solutions <aacraid@adaptec.com>
> MAINTAINERS:M: dm-devel@redhat.com
> MAINTAINERS:M: Intel Linux Wireless <ilw@linux.intel.com>
> MAINTAINERS:M: Intel SCU Linux support <intel-linux-scu@intel.com>
> MAINTAINERS:M: iscsi-driver@qlogic.com
> MAINTAINERS:M: linux-driver@qlogic.com
> MAINTAINERS:M: Linux NICS <linux.nics@intel.com>
> MAINTAINERS:M: linux-wimax@intel.com
> MAINTAINERS:M: qla2xxx-upstream@qlogic.com
> MAINTAINERS:M: Solarflare linux maintainers <linux-net-drivers@solarflare.com>
> MAINTAINERS:M: support@lsi.com
> MAINTAINERS:M: Support Opensource <support.opensource@diasemi.com>
> MAINTAINERS:M: "VMware, Inc." <pv-drivers@vmware.com>
Yeah, and in every case I've ever had to deal with one, it's never
worked. People are maintainers, not email aliases.
greg k-h
prev parent reply other threads:[~2014-06-18 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 23:09 [PATCH] MAINTAINERS: add entry for VMware Balloon driver Dmitry Torokhov
2014-06-18 23:17 ` Greg Kroah-Hartman
2014-06-18 23:19 ` Dmitry Torokhov
2014-06-18 23:28 ` Joe Perches
2014-06-18 23:49 ` Greg Kroah-Hartman [this message]
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=20140618234934.GA9378@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dtor@vmware.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pv-drivers@vmware.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