[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZAuRvXral/eNexYD@smile.fi.intel.com>
Date: Fri, 10 Mar 2023 22:23:25 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Simon Horman <simon.horman@...igine.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Kurt Kanzenbach <kurt@...utronix.de>,
Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next v5 1/1] net: dsa: hellcreek: Get rid of custom
led_init_default_state_get()
On Fri, Mar 10, 2023 at 09:16:29PM +0100, Simon Horman wrote:
> On Fri, Mar 10, 2023 at 10:06:00PM +0200, Andy Shevchenko wrote:
> > On Fri, Mar 10, 2023 at 08:44:05PM +0200, Andy Shevchenko wrote:
> > > On Fri, Mar 10, 2023 at 07:18:42PM +0100, Simon Horman wrote:
> > > > On Fri, Mar 10, 2023 at 06:38:55PM +0200, Andy Shevchenko wrote:
...
> > > > This seems to duplicate the logic in the earlier hunk of this patch.
> > > > Could it be moved into a helper?
> > >
> > > It's possible, but in a separate patch as it's out of scope of this one.
> > > Do you want to create a such?
> >
> > FWIW, I tried and it gives us +9 lines of code. So, what would be the point?
> > I can send as RFC in v6.
>
> Less duplication is good, IMHO. But it's not a hard requirement from my side.
With what I see as PoC it becomes:
a) longer (+9 LoCs);
b) less understandable.
So, I would wait for maintainers to tell me if I need this at all.
Thank you for the review!
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists