[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aFFVvjM4Dho863x2@black.fi.intel.com>
Date: Tue, 17 Jun 2025 14:47:10 +0300
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Matti Vaittinen <mazziesaccount@...il.com>
Cc: Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
Claudiu Manoil <claudiu.manoil@....com>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net-next: gianfar: Use
device_get_named_child_node_count()
On Tue, Jun 17, 2025 at 01:58:26PM +0300, Matti Vaittinen wrote:
> We can avoid open-coding the loop construct which counts firmware child
> nodes with a specific name by using the newly added
> device_get_named_child_node_count().
>
> The gianfar driver has such open-coded loop. Replace it with the
> device_get_child_node_count_named().
Just a side note: The net-next is assumed to be in the square brackets, so when
you format patch, use something like
git format-patch --subject-prefix="PATCH, net-next" ...
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists