From: Joe Perches <joe@perches.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: davem@davemloft.net,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com,
Shannon Nelson <shannon.nelson@intel.com>,
PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com>,
e1000-devel@lists.sourceforge.net
Subject: Re: [net 8/8] i40e: include i40e in kernel proper
Date: Wed, 11 Sep 2013 05:20:02 -0700 [thread overview]
Message-ID: <1378902002.606.42.camel@joe-AO722> (raw)
In-Reply-To: <1378893056-4821-9-git-send-email-jeffrey.t.kirsher@intel.com>
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?
next prev parent reply other threads:[~2013-09-11 12:20 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 [this message]
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
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=1378902002.606.42.camel@joe-AO722 \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.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).