From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com, john.ronciak@intel.com
Subject: Re: [net 0/3][pull request] Intel Wired LAN Driver Updates 2016-04-05
Date: Tue, 05 Apr 2016 19:32:07 -0400 (EDT) [thread overview]
Message-ID: <20160405.193207.578434226969621212.davem@davemloft.net> (raw)
In-Reply-To: <1459895451-45300-1-git-send-email-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Tue, 5 Apr 2016 15:30:48 -0700
> This series contains updates to i40e and e1000.
Pulled, thanks Jeff.
prev parent reply other threads:[~2016-04-05 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 22:30 [net 0/3][pull request] Intel Wired LAN Driver Updates 2016-04-05 Jeff Kirsher
2016-04-05 22:30 ` [net 1/3] i40e: fix errant PCIe bandwidth message Jeff Kirsher
2016-04-05 22:30 ` [net 2/3] e1000: Do not overestimate descriptor counts in Tx pre-check Jeff Kirsher
2016-04-05 22:30 ` [net 3/3] e1000: Double Tx descriptors needed check for 82544 Jeff Kirsher
2016-04-05 23:32 ` David Miller [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=20160405.193207.578434226969621212.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.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).