All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: joe@perches.com, netdev@vger.kernel.org,
	linux-net-drivers@solarflare.com
Subject: Re: [PATCH 7/7] MAINTAINERS: update information for sfc network driver
Date: Thu, 27 Aug 2009 13:23:19 +0100	[thread overview]
Message-ID: <1251375799.2786.9.camel@achroite> (raw)
In-Reply-To: <20090826.180445.102441324.davem@davemloft.net>

On Wed, 2009-08-26 at 18:04 -0700, David Miller wrote:
> From: Joe Perches <joe@perches.com>
> Date: Wed, 26 Aug 2009 11:47:47 -0700
> 
> > On Wed, 2009-08-26 at 19:19 +0100, Ben Hutchings wrote:
> >> Update the current maintainers and add our email addresses.  Robert
> >> Stonehouse has moved on to other projects.
> >> 
> >> Move the linux-net-drivers alias to the top since it should always
> >> reach the current maintainers at Solarflare.  Add netdev as the
> >> relevant mailing list.
> > []
> >> +M:	linux-net-drivers@solarflare.com (alias for current maintainers)
> > 
> > Hi Ben
> > 
> > This form: "M:	bare address (extra stuff)" doesn't work
> > with the get_maintainers script.
> > 
> > Can you please use something like this instead?
> > 
> > M:	Solarflare linux maintainers <linux-net-drivers@solarflare.com>
> > 
> > Perhaps this diff below.
> 
> Joe's version seems based upon reasonable requests, so I've
> applied his diff.
> 
> Thanks.

Ack, and thanks.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.


      reply	other threads:[~2009-08-27 12:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 18:19 [PATCH 7/7] MAINTAINERS: update information for sfc network driver Ben Hutchings
2009-08-26 18:47 ` Joe Perches
2009-08-27  1:04   ` David Miller
2009-08-27 12:23     ` Ben Hutchings [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=1251375799.2786.9.camel@achroite \
    --to=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --cc=linux-net-drivers@solarflare.com \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.