From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com, john.ronciak@intel.com
Subject: Re: [net-next v2 00/14][pull request] 10GbE Intel Wired LAN Driver Updates 2016-04-04
Date: Mon, 04 Apr 2016 18:45:54 -0700 [thread overview]
Message-ID: <1459820754.2965.4.camel@intel.com> (raw)
In-Reply-To: <20160404.213504.1349389173676245770.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
On Mon, 2016-04-04 at 21:35 -0400, David Miller wrote:
> From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Date: Mon, 4 Apr 2016 17:58:51 -0700
>
> >
> > This series contains updates to ixgbe and ixgbevf.
> Pulled, thanks Jeff.
Dave, I f*'d up and forgot to push v2 to my kernel.org tree before you
pulled. I have updated my 10GbE branch with the v2 series, if re-
pulling cause issues.
If it will be problematic, I can add Alex's "fixup" patch to my next
series.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-05 1:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 0:58 [net-next v2 00/14][pull request] 10GbE Intel Wired LAN Driver Updates 2016-04-04 Jeff Kirsher
2016-04-05 0:58 ` [net-next v2 01/14] ixgbe: on recv increment rx.ring->stats.yields Jeff Kirsher
2016-04-05 0:58 ` [net-next v2 02/14] ixgbevf: use bit operations for setting and checking resets Jeff Kirsher
2016-04-05 0:58 ` [net-next v2 03/14] ixgbe: Extend trust to allow guest to set unicast address Jeff Kirsher
2016-04-05 0:58 ` [net-next v2 04/14] ixgbe: Do not allow PF to add VLVF entry unless it actually needs it Jeff Kirsher
2016-04-05 0:58 ` [net-next v2 05/14] ixgbe: Avoid adding VLAN 0 twice to VLVF and VFTA Jeff Kirsher
2016-04-05 0:58 ` [net-next v2 06/14] ixgbe: Make all unchanging ops structures const Jeff Kirsher
2016-04-05 0:58 ` [net-next v2 07/14] ixgbe: use eth_platform_get_mac_address() Jeff Kirsher
2016-04-05 0:58 ` [net-next v2 08/14] ixgbe: Add support for generic Tx checksums Jeff Kirsher
2016-04-05 0:59 ` [net-next v2 09/14] ixgbevf: " Jeff Kirsher
2016-04-05 0:59 ` [net-next v2 10/14] ixgbe: Fix flow control for Xeon D KR backplane Jeff Kirsher
2016-04-05 0:59 ` [net-next v2 11/14] ixgbe: add a callback to set the maximum transmit bitrate Jeff Kirsher
2016-04-05 0:59 ` [net-next v2 12/14] ixgbe: Place SWFW semaphore in known valid state at probe Jeff Kirsher
2016-04-05 0:59 ` [net-next v2 13/14] ixgbe: Extend cls_u32 offload to support UDP headers Jeff Kirsher
2016-04-05 0:59 ` [net-next v2 14/14] ixgbe: Add support for toggling VLAN filtering flag via ethtool Jeff Kirsher
2016-04-05 1:35 ` [net-next v2 00/14][pull request] 10GbE Intel Wired LAN Driver Updates 2016-04-04 David Miller
2016-04-05 1:45 ` Jeff Kirsher [this message]
2016-04-05 2:02 ` David Miller
2016-04-05 2:04 ` 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=1459820754.2965.4.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--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).