[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250618104251.GD1699@horms.kernel.org>
Date: Wed, 18 Jun 2025 11:42:51 +0100
From: Simon Horman <horms@...nel.org>
To: Andy Shevchenko <andriy.shevchenko@...el.com>
Cc: Matti Vaittinen <mazziesaccount@...il.com>,
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>,
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 02:47:10PM +0300, Andy Shevchenko wrote:
> 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" ...
Hi Matti,
It looks like this patch has been marked as Changes Requested in patchwork.
I assume because of Andy's comment above.
Could you address that and submit a v2?
Subject: [PATCH net-next v2] ...
Otherwise, this looks good to me.
Powered by blists - more mailing lists