netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, gospo@redhat.com, bphilips@novell.com
Subject: Re: [net-next-2.6 00/11][pull request] Intel Wired LAN Driver Updates
Date: Fri, 11 Mar 2011 15:03:38 -0800 (PST)	[thread overview]
Message-ID: <20110311.150338.193701255.davem@davemloft.net> (raw)
In-Reply-To: <1299854851.2852.7.camel@jtkirshe-MOBL1>

From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Fri, 11 Mar 2011 06:47:31 -0800

> On Fri, 2011-03-11 at 11:06 -0800, David Miller wrote:
>> From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>> Date: Fri, 11 Mar 2011 03:06:19 -0800
>> 
>> > The following series contains FCoE documentation update, ixgb conversion
>> > to the new VLAN model, several fixes and cleanups for e1000e and
>> > the removal of Tx hang detection in ixgbevf (like recent igbvf patch).
>> > 
>> > The following are changes since commit 1b7fe59322bef9e7a2c05b64a07a66b875299736:
>> >   ipv4: Kill flowi arg to fib_select_multipath()
>> > 
>> > and are available in the git repository at:
>> >   master.kernel.org:/pub/scm/linux/kernel/git/jkirsher/net-next-2.6 master
>> 
>> Does this one actually compile? :-)
> 
> Yes, it does.  Sorry about the last one, both Emil and I had found the
> issue when I applied the patch to my internal testing tree and I
> manually fixed up the compile issue, but forgot to send out the updated
> patch to our patchwork server.
> 
> I personally double checked the compilation of every single patch in
> this pull request.

Ok, good to hear, pulled :-)

      reply	other threads:[~2011-03-11 23:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 11:06 [net-next-2.6 00/11][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2011-03-11 11:06 ` [net-next-2.6 01/11] ixgb: convert to new VLAN model Jeff Kirsher
2011-03-11 11:06 ` [net-next-2.6 02/11] net: add proper documentation for previously added net_device_ops for FCoE Jeff Kirsher
2011-03-11 11:06 ` [net-next-2.6 03/11] ixgbevf: remove Tx hang detection Jeff Kirsher
2011-03-11 11:06 ` [net-next-2.6 04/11] e1000e: use dev_kfree_skb_irq() instead of dev_kfree_skb() Jeff Kirsher
2011-03-11 11:06 ` [net-next-2.6 05/11] e1000e: magic number cleanup - ETH_ALEN Jeff Kirsher
2011-03-11 11:06 ` [net-next-2.6 06/11] e1000e: extend timeout for ethtool link test diagnostic Jeff Kirsher
2011-03-11 11:06 ` [net-next-2.6 07/11] e1000e: extend EEE LPI timer to prevent dropped link Jeff Kirsher
2011-03-11 11:06 ` [net-next-2.6 08/11] e1000e: do not toggle LANPHYPC value bit when PHY reset is blocked Jeff Kirsher
2011-03-11 11:06 ` [net-next-2.6 09/11] e1000e: disable jumbo frames on 82579 when MACsec enabled in EEPROM Jeff Kirsher
2011-03-11 11:06 ` [net-next-2.6 10/11] e1000e: do not suggest the driver supports Wake-on-ARP Jeff Kirsher
2011-03-11 11:06 ` [net-next-2.6 11/11] e1000e: bump version number Jeff Kirsher
2011-03-11 19:06 ` [net-next-2.6 00/11][pull request] Intel Wired LAN Driver Updates David Miller
2011-03-11 14:47   ` Jeff Kirsher
2011-03-11 23:03     ` 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=20110311.150338.193701255.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bphilips@novell.com \
    --cc=gospo@redhat.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=netdev@vger.kernel.org \
    /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).