[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100921.162326.226765001.davem@davemloft.net>
Date: Tue, 21 Sep 2010 16:23:26 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: bhutchings@...arflare.com
Cc: netdev@...r.kernel.org, linux-net-drivers@...arflare.com
Subject: Re: [PATCH net-next-2.6 0/8] sfc and ethtool changes for 2.6.37
From: David Miller <davem@...emloft.net>
Date: Tue, 21 Sep 2010 14:58:27 -0700 (PDT)
> From: Ben Hutchings <bhutchings@...arflare.com>
> Date: Mon, 20 Sep 2010 19:40:56 +0100
>
>> This series adds Ethernet-level filtering and explicit filter clearing
>> to the ethtool RX n-tuple interface, and implements it in the sfc
>> driver.
>>
>> There is a cleanup patch on the end which is preparation for the
>> following RFC patch series but is worthwhile anyway.
>>
>> Ben Hutchings (8):
>> ethtool: Define RX n-tuple action to clear a rule
>> ethtool: Add Ethernet MAC-level filtering/steering
>> ethtool: Allocate register dump buffer with vmalloc()
>> sfc: Add filter table management
>> sfc: Implement the ethtool RX n-tuple control functions
>> sfc: Include RX IP filter table in register dump
>> sfc: Set net_device::num_rx_queues once we know the correct value
>> sfc: Clean up and correct comments on efx_monitor()
>
> All applied except patch #7 as noted in the thread for that patch.
Ben, just FYI, I had to add "linux/vmalloc.h" includes to both
net/core/ethtool.c and drivers/net/sfc/net_driver.h otherwise
the build breaks on some architectures.
x86 can be a really bad arch to validates builds on because it
currently gets vmalloc.h implicitly by some of it's core header files.
In particular, asm/io.h :-/
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists