From: Ben Hutchings <bhutchings@solarflare.com>
To: netdev@vger.kernel.org, "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Subject: [PATCH ethtool 0/3] Regularise handling of offload flags
Date: Mon, 21 Feb 2011 16:54:42 +0000 [thread overview]
Message-ID: <1298307282.2608.47.camel@bwh-desktop> (raw)
This patch series is partly inspired by the recent changes to regularise
the relationship between ethtool offload control and net_device feature
flags, though I started on it earlier.
I don't intend to apply these changes until after the kernel and ethtool
v2.6.38 releases. In the mean time, I would appreciate testing and
feedback.
Ben.
Ben Hutchings (3):
ethtool-copy.h: sync with net-next-2.6
ethtool: Regularise handling of offload flags
ethtool: Report additional offload flag changes made automatically
ethtool-copy.h | 89 +++++++++++-
ethtool-util.h | 30 ++++
ethtool.c | 465 ++++++++++++++++++++++++++++----------------------------
3 files changed, 352 insertions(+), 232 deletions(-)
--
1.7.3.4
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
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-02-21 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 16:54 Ben Hutchings [this message]
2011-02-21 16:57 ` [PATCH ethtool 1/3] ethtool-copy.h: sync with net-next-2.6 Ben Hutchings
2011-02-21 16:59 ` [PATCH ethtool 2/3] ethtool: Regularise handling of offload flags Ben Hutchings
2011-02-22 14:50 ` Michał Mirosław
2011-02-22 16:44 ` Ben Hutchings
2011-02-22 17:03 ` Michał Mirosław
2011-02-22 21:17 ` Michał Mirosław
2011-02-23 3:03 ` Michał Mirosław
2011-02-21 16:59 ` [PATCH ethtool 3/3] ethtool: Report additional offload flag changes made automatically Ben Hutchings
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=1298307282.2608.47.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=mirq-linux@rere.qmqm.pl \
--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