[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190504025353.74acbb6d@cakuba.netronome.com>
Date: Sat, 4 May 2019 02:53:53 -0400
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Maxime Chevallier <maxime.chevallier@...tlin.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Antoine Tenart <antoine.tenart@...tlin.com>,
thomas.petazzoni@...tlin.com, gregory.clement@...tlin.com,
miquel.raynal@...tlin.com, nadavh@...vell.com, stefanc@...vell.com,
mw@...ihalf.com, Russell King <linux@...linux.org.uk>,
linux-arm-kernel@...ts.infradead.org,
Saeed Mahameed <saeedm@...lanox.com>
Subject: Re: [PATCH net-next 0/4] net: mvpp2: cls: Add classification
On Tue, 30 Apr 2019 15:14:25 +0200, Maxime Chevallier wrote:
> Compared to the first submissions, the NETIF_F_NTUPLE flag was also
> removed, following Saeed's comment.
You should probably add it back, even though the stack only uses
NETIF_F_NTUPLE for aRFS the ethtool APIs historically depend on the
drivers doing a lot of the validation.
The flag was added by:
15682bc488d4 ("ethtool: Introduce n-tuple filter programming support")
your initial use of the flag was correct.
Powered by blists - more mailing lists