From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
linux-net-drivers <linux-net-drivers@solarflare.com>
Subject: pull request: sfc-next-2.6 2011-05-17
Date: Tue, 17 May 2011 16:59:48 +0100 [thread overview]
Message-ID: <1305647988.2848.14.camel@bwh-desktop> (raw)
The following changes since commit 7be799a70ba3dd90a59e8d2c72bbe06020005b3f:
ipv4: Remove rt->rt_dst reference from ip_forward_options(). (2011-05-13 17:31:02 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc-next-2.6.git master
Miscellaneous bug fixes.
Ben.
Ben Hutchings (3):
sfc: Fix return value from efx_ethtool_set_rx_ntuple()
sfc: Fix TX queue numbering when separate_tx_channels=1
sfc: Use netif_device_{detach,attach}() around reset and self-test
drivers/net/sfc/efx.c | 21 +++++++++++++++------
drivers/net/sfc/ethtool.c | 5 +++--
drivers/net/sfc/net_driver.h | 4 +---
drivers/net/sfc/selftest.c | 11 +++++------
drivers/net/sfc/tx.c | 9 +++++----
5 files changed, 29 insertions(+), 21 deletions(-)
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next reply other threads:[~2011-05-17 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 15:59 Ben Hutchings [this message]
2011-05-17 16:04 ` [PATCH net-next-2.6 1/3] sfc: Fix return value from efx_ethtool_set_rx_ntuple() Ben Hutchings
2011-05-17 16:05 ` [PATCH net-next-2.6 2/3] sfc: Fix TX queue numbering when separate_tx_channels=1 Ben Hutchings
2011-05-17 16:06 ` [PATCH net-next-2.6 3/3] sfc: Use netif_device_{detach,attach}() around reset and self-test Ben Hutchings
2011-05-17 18:00 ` pull request: sfc-next-2.6 2011-05-17 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=1305647988.2848.14.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-net-drivers@solarflare.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).