From: Rick Jones <rick.jones2@hp.com>
To: jeffrey.t.kirsher@intel.com
Cc: Joe Perches <joe@perches.com>,
Tushar Dave <tushar.n.dave@intel.com>,
davem@davemloft.net,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com
Subject: Re: [net-next 2/8] maintainers: update with official intel support link, new maintainer
Date: Wed, 24 Oct 2012 10:31:05 -0700 [thread overview]
Message-ID: <508825D9.6020306@hp.com> (raw)
In-Reply-To: <1351053166.2252.39.camel@jtkirshe-mobl>
On 10/23/2012 09:32 PM, Jeff Kirsher wrote:
> So how do we go about giving this spider web of complex coverage to some
> clear concise coverage in the MAINTAINERS?
I happen to like seeing "real" names. Is it possible to leverage email
conventions to allow a comment of sorts with each email:
INTEL ETHERNET DRIVERS (e100/e1000/e1000e/igb/igbvf/ixgb/ixgbe/ixgbevf)
M: Jeff Kirsher (den mother) <jeffrey.t.kirsher@intel.com>
M: Jesse Brandeburg (performance focus) <jesse.brandeburg@intel.com>
M: Bruce Allan (e1000e focus) <bruce.w.allan@intel.com>
M: Carolyn Wyborny (igb focus) <carolyn.wyborny@intel.com>
M: Don Skidmore (omnibus) <donald.c.skidmore@intel.com>
M: Greg Rose (omnibus) <gregory.v.rose@intel.com>
M: Peter P Waskiewicz Jr (omnibus) <peter.p.waskiewicz.jr@intel.com>
M: Alex Duyck (omnibus) <alexander.h.duyck@intel.com>
M: John Ronciak (omnibus) <john.ronciak@intel.com>
M: Tushar Dave (omnibus and rca) <tushar.n.dave@intel.com>
perhaps "any" or "all" rather than omnibus if that is too much a
fifty-cent word. Everyone is still in one place, but with some
indication of specialization/generalization. If the parenthesis form
cannot be used, (I've not seen it elsewhere in MAINTAINERS) then perhaps
the quoted form.
rick jones
(And yes, "den mother" was meant as a bit of levity :)
next prev parent reply other threads:[~2012-10-24 17:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 10:24 [net-next 0/8][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2012-10-23 10:24 ` [net-next 1/8] e1000e: Minimum packet size must be 17 bytes Jeff Kirsher
2012-10-23 15:25 ` David Laight
2012-10-23 16:37 ` Alexander Duyck
2012-10-23 10:24 ` [net-next 2/8] maintainers: update with official intel support link, new maintainer Jeff Kirsher
2012-10-23 13:25 ` Joe Perches
2012-10-24 4:32 ` Jeff Kirsher
2012-10-24 4:52 ` Joe Perches
2012-10-24 5:13 ` Jeff Kirsher
2012-10-24 17:31 ` Rick Jones [this message]
2012-10-23 10:24 ` [net-next 3/8] igb: Update get cable length function for i210/i211 Jeff Kirsher
2012-10-23 10:24 ` [net-next 4/8] igb: Update version Jeff Kirsher
2012-10-23 10:24 ` [net-next 5/8] ixgbevf: make netif_napi_add and netif_napi_del symmetric Jeff Kirsher
2012-10-23 10:24 ` [net-next 6/8] ixgbevf: Check for error on dma_map_single call Jeff Kirsher
2012-10-23 10:24 ` [net-next 7/8] ixgbevf: fix softirq-safe to unsafe splat on internal mbx_lock Jeff Kirsher
2012-10-23 10:24 ` [net-next 8/8] ixgbevf: Update version string Jeff Kirsher
2012-10-23 17:28 ` [net-next 0/8][pull request] Intel Wired LAN Driver Updates David Miller
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=508825D9.6020306@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.com \
--cc=tushar.n.dave@intel.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 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.