netdev - Re: [PATCHv2 net-next 0/8] RX NFC support for hash-based filters

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1325713170.3764.2.camel@bwh-desktop>
Date:	Wed, 4 Jan 2012 21:39:30 +0000
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	David Miller <davem@...emloft.net>
CC:	<netdev@...r.kernel.org>, <linux-net-drivers@...arflare.com>
Subject: Re: [PATCHv2 net-next 0/8] RX NFC support for hash-based filters

On Wed, 2012-01-04 at 14:11 -0500, David Miller wrote:
> From: Ben Hutchings <bhutchings@...arflare.com>
> Date: Tue, 3 Jan 2012 21:56:59 +0000
> 
> > 1. Fix gianfar's validation of filter rule locations.  In the previous
> >    version of this series, this was a requirement for part 2, but that's
> >    no longer the case.
> > 
> > 2. Extend ethtool RX NFC rules API to support hash-based filter hardware
> >    in which rule locations should be selected by the driver or firmware.
> > 
> > 3. Change the sfc driver to implement this API instead of RX n-tuple.
> > 
> > 4. Remove support for RX n-tuple, now that there are no in-tree
> >    implementations.
> 
> All applied, I had to fix some trailing whitespace errors in patches
> 5 and 6.

Thanks, and sorry about the formatting.  I should try to work out why
git didn't alert me to that earlier...

Ben.

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

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