All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [RFT PATCH 0/9] Cleanup and extension of netdev features
Date: Tue, 21 Jun 2011 22:52:03 +0100	[thread overview]
Message-ID: <1308693123.2743.71.camel@bwh-desktop> (raw)
In-Reply-To: <4E011080.7000008@candelatech.com>

On Tue, 2011-06-21 at 14:43 -0700, Ben Greear wrote:
> On 06/20/2011 12:14 PM, Michał Mirosław wrote:
> > This is a preview of the cleanups pending after getting rid of old
> > ethtool ops from remaining drivers.
> 
> Even when skipping patch 1 (seems this was just merged earlier today),
> these patches do not all apply to net-next.
> 
> They are also full of white-space warnings.
> 
> Please re-post them when you sync against upstream
> and I'll try to do some testing.
> 
> Also, do you have a cooresponding patch against ethtool
> to make it able to handle the new 64-bit flags?

It doesn't handle named features at all yet, though Michał has
previously prepared patches to do so.

Ben.

-- 
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.


  reply	other threads:[~2011-06-21 21:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 19:14 [RFT PATCH 0/9] Cleanup and extension of netdev features Michał Mirosław
2011-06-20 19:14 ` [RFT PATCH 4/9] net: introduce and use netdev_features_t for device features sets Michał Mirosław
2011-06-20 21:01   ` Ben Hutchings
2011-06-20 19:14 ` [RFT PATCH 2/9] net: remove legacy ethtool ops Michał Mirosław
2011-06-20 19:14 ` [RFT PATCH 3/9] net: ethtool: break association of ETH_FLAG_* with NETIF_F_* Michał Mirosław
2011-06-20 20:11   ` Ben Hutchings
2011-06-20 20:27     ` David Miller
2011-06-20 20:51     ` Stephen Hemminger
2011-06-20 20:52       ` David Miller
2011-06-20 21:30         ` Ben Hutchings
2011-06-20 19:14 ` [RFT PATCH 5/9] net: Define enum for net device features Michał Mirosław
2011-06-20 19:14 ` [RFT PATCH 9/9] net: move NOCACHE_COPY checks to netdev_fix_features() Michał Mirosław
2011-06-20 19:14 ` [RFT PATCH 8/9] net: extend netdev_features_t to 64 bits Michał Mirosław
2011-06-20 19:14 ` [RFT PATCH 7/9] ethtool: prepare for larger netdev_features_t type Michał Mirosław
2011-06-20 21:16   ` Ben Hutchings
2011-06-23 17:50     ` Mahesh Bandewar
2011-06-23 18:03       ` Ben Hutchings
2011-06-23 18:21         ` Mahesh Bandewar
2011-06-23 18:55           ` Ben Hutchings
2011-06-23 20:38             ` Mahesh Bandewar
2011-06-20 19:14 ` [RFT PATCH 6/9] net: ethtool: use C99 array initialization for feature-names table Michał Mirosław
2011-06-20 19:35 ` [RFT PATCH 0/9] Cleanup and extension of netdev features David Miller
2011-06-20 19:47   ` Michał Mirosław
2011-06-20 19:55     ` [IGNORE PATCH 1/9] Intel net drivers: convert to ndo_fix_features Michał Mirosław
2011-06-21 21:43 ` [RFT PATCH 0/9] Cleanup and extension of netdev features Ben Greear
2011-06-21 21:52   ` Ben Hutchings [this message]
2011-06-21 23:27   ` Jeff Kirsher
2011-06-23 17:42 ` Mahesh Bandewar

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=1308693123.2743.71.camel@bwh-desktop \
    --to=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=greearb@candelatech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.