[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <976cbd32-3f0c-4ca4-b147-10040f2d7767@intel.com>
Date: Thu, 26 Oct 2023 16:18:03 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: Florian Fainelli <florian.fainelli@...adcom.com>,
<netdev@...r.kernel.org>
CC: Doug Berger <opendmb@...il.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@...adcom.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
Vladimir Oltean <vladimir.oltean@....com>,
"Tariq Toukan" <tariqt@...dia.com>, Gal Pressman <gal@...dia.com>,
Willem de Bruijn <willemb@...gle.com>,
Daniil Tatianin <d-tatianin@...dex-team.ru>,
"Simon Horman" <horms@...nel.org>,
Justin Chen <justin.chen@...adcom.com>,
"Ratheesh Kannoth" <rkannoth@...vell.com>,
Joe Damato <jdamato@...tly.com>,
"Vincent Mailhol" <mailhol.vincent@...adoo.fr>,
Jiri Pirko <jiri@...nulli.us>,
"open list" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next v2 1/5] net: ethtool: Make RXNFC walking code
accept a callback
On 10/26/2023 3:45 PM, Florian Fainelli wrote:
> In preparation for iterating over RXNFC rules for a different purpose,
> factor the generic code that already does that by allowing a callback to
> be specified. The body of ethtool_get_max_rxnfc_channel() now accepts a
> callback as an argument and is renamed to __ethtool_for_each_rxnfc().
>
> Signed-off-by: Florian Fainelli <florian.fainelli@...adcom.com>
Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
Powered by blists - more mailing lists