[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZPX3ZqCV2tKh2zkH@baltimore>
Date: Mon, 4 Sep 2023 17:27:34 +0200
From: Pawel Chmielewski <pawel.chmielewski@...el.com>
To: Andrew Lunn <andrew@...n.ch>
CC: Alexander Lobakin <aleksander.lobakin@...el.com>, "Greenwalt, Paul"
<paul.greenwalt@...el.com>, <aelior@...vell.com>,
<intel-wired-lan@...ts.osuosl.org>, <manishc@...vell.com>,
<netdev@...r.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 2/9] ethtool: Add forced
speed to supported link modes maps
On Sun, Sep 03, 2023 at 04:00:57PM +0200, Andrew Lunn wrote:
> > Let me check if I understand correctly- is that what was sent with the
> > v3 [1] , with the initialization helper (ethtool_forced_speed_maps_init)
> > and the structure map in the ethtool code? Or do you have another helper
> > in mind?
>
> Sorry for the late reply, been on vacation.
>
> The main thing is you try to reuse the table:
>
> static const struct phy_setting settings[] = {}
>
> If you can build your helper on top of phy_lookup_setting() even
> better. You don't need a phy_device to use those.
>
> Andrew
Thank you for the clarification, I'll write it and propose in the next version.
Most probably split this refactoring from the original series.
Pawel
Powered by blists - more mailing lists