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/21][pull request] Intel Wired LAN Driver Updates
Date: Sat, 12 Mar 2011 14:42:19 -0800 (PST) [thread overview]
Message-ID: <20110312.144219.104054672.davem@davemloft.net> (raw)
In-Reply-To: <1299932428-3114-1-git-send-email-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Sat, 12 Mar 2011 04:20:07 -0800
> The following series contains a version string fix and bump for ixgbevf,
> added functionality for i350 devices in igb, and cleanups and fixes in
> ixgbe (mainly DCB changes).
>
> The following are changes since commit 70d279a7e2a6e308530822ba2bf4134cc0f5c091:
> e1000e: bump version number
> and are available in the git repository at:
> master.kernel.org:/pub/scm/linux/kernel/git/jkirsher/net-next-2.6 master
Looks good, pulled, thanks Jeff.
prev parent reply other threads:[~2011-03-12 22:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 12:20 [net-next-2.6 00/21][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 01/21] ixgbevf: Fix Version String Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 02/21] ixgbevf: Fix Driver String Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 03/21] igb: Add Energy Efficient Ethernet (EEE) for i350 devices Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 04/21] igb: Update NVM functions to work with " Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 05/21] igb: Add DMA Coalescing feature to driver Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 06/21] igb: Bump version to 3.0.6 Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 07/21] ixgbe: DCB, implement capabilities flags Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 08/21] ixgbe: DCB, implement ieee_setapp dcbnl ops Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 09/21] ixgbe: DCB remove ixgbe_fcoe_getapp routine Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 10/21] ixgbe: DCB, use multiple Tx rings per traffic class Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 11/21] ixgbe: enable ndo_tc_setup Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 12/21] ixgbe: DCB: enable RSS to be used with DCB Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 13/21] ixgbe: DCB, missed translation from 8021Qaz TSA to CEE link strict Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 14/21] ixgbe: IEEE 802.1Qaz, implement priority assignment table Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 15/21] ixgbe: DCB during ifup use correct CEE or IEEE mode Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 16/21] ixgbe: remove timer reset to 0 on timeout Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 17/21] ixgbe: update PHY code to support 100Mbps as well as 1G/10G Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 18/21] ixgbe: correct typo in define name Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 19/21] ixgbe: DCB, set minimum bandwidth per traffic class Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 20/21] ixgbe: add support for VF Transmit rate limit using iproute2 Jeff Kirsher
2011-03-12 12:20 ` [net-next-2.6 21/21] ixgbe: DCB, PFC not cleared until reset occurs Jeff Kirsher
2011-03-12 22:42 ` 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=20110312.144219.104054672.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).