From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com
Subject: Re: [net-next 0/4][pull request] Intel Wired LAN Driver Updates
Date: Tue, 18 Sep 2012 23:03:55 -0700 [thread overview]
Message-ID: <1348034635.2006.52.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1348029108-26659-1-git-send-email-jeffrey.t.kirsher@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
On Tue, 2012-09-18 at 21:31 -0700, Jeff Kirsher wrote:
> This series contains updates to igb and ixgbevf.
>
> The following are changes since commit adccff34de1ef81564b7e6c436f762e7a1caf807:
> net/tipc/name_table.c: Remove unecessary semicolon
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/net-next master
>
> Akeem G. Abodunrin (1):
> igb: Support to enable EEE on all eee_supported devices
>
> Alexander Duyck (2):
> igb: Remove artificial restriction on RQDPC stat reading
> ixgbevf: Add support for VF API negotiation
>
> John Fastabend (1):
> ixgbevf: scheduling while atomic in reset hw path
>
> drivers/net/ethernet/intel/igb/e1000_82575.c | 17 +++++++---
> drivers/net/ethernet/intel/igb/e1000_defines.h | 3 +-
> drivers/net/ethernet/intel/igb/e1000_regs.h | 1 +
> drivers/net/ethernet/intel/igb/igb_main.c | 8 +++--
> drivers/net/ethernet/intel/ixgbevf/defines.h | 1 +
> drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 23 +++++++++++++
> drivers/net/ethernet/intel/ixgbevf/mbx.h | 21 ++++++++++--
> drivers/net/ethernet/intel/ixgbevf/vf.c | 39 ++++++++++++++++++++++-
> drivers/net/ethernet/intel/ixgbevf/vf.h | 3 ++
> 9 files changed, 105 insertions(+), 11 deletions(-)
>
Dave,
Do not pull, it appears there will be changes to patch 04 of the series,
I will be sending a v2 of the series once John gets patch 04 fixed up.
Cheers,
Jeff
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-09-19 6:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 4:31 [net-next 0/4][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2012-09-19 4:31 ` [net-next 1/4] igb: Remove artificial restriction on RQDPC stat reading Jeff Kirsher
2012-09-19 4:31 ` [net-next 2/4] igb: Support to enable EEE on all eee_supported devices Jeff Kirsher
2012-09-19 4:31 ` [net-next 3/4] ixgbevf: Add support for VF API negotiation Jeff Kirsher
2012-09-19 4:31 ` [net-next 4/4] ixgbevf: scheduling while atomic in reset hw path Jeff Kirsher
2012-09-19 5:05 ` Eric Dumazet
2012-09-19 6:03 ` Jeff Kirsher [this message]
2012-09-19 6:19 ` [net-next 0/4][pull request] Intel Wired LAN Driver Updates David Miller
-- strict thread matches above, loose matches on Subject: below --
2012-09-05 6:25 Jeff Kirsher
2012-09-05 19:10 ` David Miller
2012-05-17 11:27 Jeff Kirsher
2012-05-17 11:51 ` Jeff Kirsher
2012-05-17 19:12 ` David Miller
2012-05-05 12:38 Jeff Kirsher
2012-05-06 17:25 ` David Miller
2012-05-07 7:12 ` Jeff Kirsher
2012-05-07 16:33 ` David Miller
2012-03-03 2:26 Jeff Kirsher
2012-03-03 19:53 ` David Miller
2012-03-03 2:24 Jeff Kirsher
2012-03-03 2:27 ` Jeff Kirsher
2011-01-22 11:56 Jeff Kirsher
2011-01-24 8:19 ` Jeff Kirsher
2011-01-24 21:02 ` 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=1348034635.2006.52.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=netdev@vger.kernel.org \
--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).