netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Cc: Joe Perches <joe@perches.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"gospo@redhat.com" <gospo@redhat.com>,
	"sassmann@redhat.com" <sassmann@redhat.com>,
	"Nelson, Shannon" <shannon.nelson@intel.com>,
	"e1000-devel@lists.sourceforge.net"
	<e1000-devel@lists.sourceforge.net>
Subject: Re: [net  8/8] i40e: include i40e in kernel proper
Date: Wed, 11 Sep 2013 08:37:30 -0700	[thread overview]
Message-ID: <1378913850.2026.19.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1378913071.3863.27.camel@ppwaskie-mobl2>

[-- Attachment #1: Type: text/plain, Size: 671 bytes --]

On Wed, 2013-09-11 at 08:24 -0700, Waskiewicz Jr, Peter P wrote:
> On Wed, 2013-09-11 at 05:20 -0700, Joe Perches wrote:
> > On Wed, 2013-09-11 at 02:50 -0700, Jeff Kirsher wrote:
> > > New driver build option is CONFIG_I40E
> > 
> > > diff --git a/Documentation/networking/00-INDEX b/Documentation/networking/00-INDEX
> > []
> > > +i40e.txt
> > > +	- README for the Intel Ethernet Controller XL710 Driver (i40e).
> > 
> > Just curious but why the XL710 / i40e name mismatch?
> 
> ixgbe is a good example.  ixgbe is the driver name, but it supports the
> 82598, 82599 / X520, and X540 chips.
> 

Another good example is e100, e1000, e1000e, and igb. :-)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-09-11 15:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11  9:50 [net v7 0/8][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2013-09-11  9:50 ` [net v7 1/8] i40e: main driver core Jeff Kirsher
2013-09-11 12:16   ` Joe Perches
2013-09-11  9:50 ` [net 2/8] i40e: transmit, receive, and NAPI Jeff Kirsher
2013-09-11  9:50 ` [net 3/8] i40e: driver ethtool core Jeff Kirsher
2013-09-11  9:50 ` [net 4/8] i40e: driver core headers Jeff Kirsher
2013-09-11  9:50 ` [net 5/8] i40e: implement virtual device interface Jeff Kirsher
2013-09-11  9:50 ` [net 6/8] i40e: init code and hardware support Jeff Kirsher
2013-09-11  9:50 ` [net 7/8] i40e: debugfs interface Jeff Kirsher
2013-09-11  9:50 ` [net 8/8] i40e: include i40e in kernel proper Jeff Kirsher
2013-09-11 12:20   ` Joe Perches
2013-09-11 14:32     ` Jeff Kirsher
2013-09-11 14:47       ` Joe Perches
2013-09-11 15:25         ` Jeff Kirsher
2013-09-11 15:31       ` Joe Perches
2013-09-11 15:24     ` Waskiewicz Jr, Peter P
2013-09-11 15:37       ` Jeff Kirsher [this message]
2013-09-11 21:08 ` [net v7 0/8][pull request] Intel Wired LAN Driver Updates David Miller
2013-09-11 22:08   ` Jeff Kirsher

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=1378913850.2026.19.camel@jtkirshe-mobl \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=davem@davemloft.net \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=gospo@redhat.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=joe@perches.com \
    --cc=netdev@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --cc=sassmann@redhat.com \
    --cc=shannon.nelson@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 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).