[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ea2635-c0b3-4de4-bc65-cbc33a0d5814@lunn.ch>
Date: Sun, 3 Sep 2023 16:00:57 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Pawel Chmielewski <pawel.chmielewski@...el.com>
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
> 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
Powered by blists - more mailing lists