From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com
Subject: Re: [net-next v2 00/10][pull request] Intel Wired LAN Driver Updates
Date: Thu, 13 Mar 2014 15:48:38 -0700 [thread overview]
Message-ID: <1394750918.2167.26.camel@jtkirshe-mobl> (raw)
In-Reply-To: <20140313.150403.1216425576381362401.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
On Thu, 2014-03-13 at 15:04 -0400, David Miller wrote:
> From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Date: Wed, 12 Mar 2014 19:31:20 -0700
>
> > This series contains updates to igb, e1000e, ixgbe and ixgbevf.
> >
> > Tom Herbert provides changes to e1000e, igb and ixgbe to call skb_set_hash()
> > to set the hash and its type in an skbuff.
> >
> > Carolyn provides a fix for igb where using ethtool for EEE settings, which
> > was not working correctly.
> >
> > Jacob provides some trivial cleanups and fixes for ixgbe which mainly
> > dealt with the file headers.
> >
> > Julia Lawall provides a one fix for ixgbevf where the driver did not need
> > to adjust the power state on suspend, so the call to pci_set_power_state()
> > in the resume function was a no-op.
> >
> > v2:
> > - dropped patches 4-6 from original series which implemented debugfs for
> > igb from Carolyn based on feed back from David Miller and Or Gerlitz
>
> Pulled, thanks a lot Jeff.
>
> BTW, from patch #3:
>
> + /*Re-establish EEE setting */
>
> There really should be a space after "/*", please fix this up in a future
> pull request.
>
> Thanks.
Putting together a patch (and series now). Thanks Dave!
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-03-13 22:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 2:31 [net-next v2 00/10][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2014-03-13 2:31 ` [net-next v2 01/10] net: e1000e calls skb_set_hash Jeff Kirsher
2014-03-13 2:31 ` [net-next v2 02/10] net: igb " Jeff Kirsher
2014-03-13 2:31 ` [net-next v2 03/10] igb: Fix for devices using ethtool for EEE settings Jeff Kirsher
2014-03-13 2:31 ` [net-next v2 04/10] net: ixgbe calls skb_set_hash Jeff Kirsher
2014-03-13 2:31 ` [net-next v2 05/10] ixgbe: Fix format string in ixgbe_fcoe.c Jeff Kirsher
2014-03-13 2:31 ` [net-next v2 06/10] ixgbe: move setting rx_pb_size into get_invariants Jeff Kirsher
2014-03-13 2:31 ` [net-next v2 07/10] ixgbe: add Linux NICS mailing list to contact info Jeff Kirsher
2014-03-13 2:31 ` [net-next v2 08/10] ixgbe: fixup header for ixgbe_set_rxpba_82598 Jeff Kirsher
2014-03-13 2:31 ` [net-next v2 09/10] ixgbe: fix some multiline hw_dbg prints Jeff Kirsher
2014-03-13 2:31 ` [net-next v2 10/10] ixgbevf: delete unneeded call to pci_set_power_state Jeff Kirsher
2014-03-13 19:04 ` [net-next v2 00/10][pull request] Intel Wired LAN Driver Updates David Miller
2014-03-13 22:48 ` Jeff Kirsher [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-23 12:59 Jeff Kirsher
2014-05-23 20:14 ` David Miller
2013-08-29 10:49 Jeff Kirsher
2013-08-29 20:14 ` 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=1394750918.2167.26.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).