netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mirq-linux@rere.qmqm.pl
Cc: netdev@vger.kernel.org, bhutchings@solarflare.com
Subject: Re: [PATCH 0/4] Fixes for unified offload configuration
Date: Wed, 23 Feb 2011 14:24:27 -0800 (PST)	[thread overview]
Message-ID: <20110223.142427.260100046.davem@davemloft.net> (raw)
In-Reply-To: <cover.1298429033.git.mirq-linux@rere.qmqm.pl>

From: Michał Mirosław <mirq-linux@rere.qmqm.pl>
Date: Wed, 23 Feb 2011 03:52:28 +0100 (CET)

> this series contains couple of fixes to ethtool unification work in net-next.
> 
> patches 1 and 2 (resend):
> 	fix following message at device registration:
> 	(unregistered net_device): features changed: 0x00011065 -> 0x00015065
> 
> patches 3 and 4:
> 	implement compatibility fallback in ethtool_{g,s}features for drivers
> 	not converted to new offload setting scheme.
> 
> only compile tested for now as my test box has some hardware issues lately.

All applied, thanks.

      parent reply	other threads:[~2011-02-23 22:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23  2:52 [PATCH 0/4] Fixes for unified offload configuration Michał Mirosław
2011-02-23  2:52 ` [PATCH 1/4] Fix "(unregistered net_device): Features changed" message Michał Mirosław
2011-02-23  2:52 ` [PATCH 2/4] net: avoid initial "Features " Michał Mirosław
2011-02-23  2:52 ` [PATCH 3/4] net: Fix ETHTOOL_GFEATURES compatibility Michał Mirosław
2011-02-23  2:52 ` [PATCH 4/4] net: Implement SFEATURES compatibility for not updated drivers Michał Mirosław
2011-02-23 22:24 ` 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=20110223.142427.260100046.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=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;
as well as URLs for NNTP newsgroup(s).