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>,
scrum-linux <scrum-linux@solarflare.com>
Subject: Pull request: sfc 2013-03-12
Date: Tue, 12 Mar 2013 17:47:25 +0000 [thread overview]
Message-ID: <1363110445.2780.14.camel@bwh-desktop.uk.solarflarecom.com> (raw)
The following changes since commit c80a8512ee3a8e1f7c3704140ea55f21dc6bd651:
net/core: move vlan_depth out of while loop in skb_network_protocol() (2013-03-12 11:47:40 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bwh/sfc.git sfc-3.9
(commit fae8563b25f73dc584a07bcda7a82750ff4f7672)
Just the one bug fix I mentioned before, but it's a pretty important one
as it can cause silent data corruption or IOMMU page faults.
This would be suitable for stable and should apply cleanly to all the
3.x.y branches. I'm still working through testing of larger sets of
fixes.
Ben.
Ben Hutchings (1):
sfc: Only use TX push if a single descriptor is to be written
drivers/net/ethernet/sfc/nic.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
--
Ben Hutchings, Staff 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:[~2013-03-12 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 17:47 Ben Hutchings [this message]
2013-03-12 17:48 ` [PATCH net] sfc: Only use TX push if a single descriptor is to be written Ben Hutchings
2013-03-13 9:17 ` Pull request: sfc 2013-03-12 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=1363110445.2780.14.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=scrum-linux@solarflare.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