[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9c4715cb-4b7f-4c0f-8170-da7a9daba7ec@gmail.com>
Date: Thu, 15 May 2025 07:38:14 +0200
From: Heiner Kallweit <hkallweit1@...il.com>
To: Jakub Kicinski <kuba@...nel.org>, Sean Anderson <sean.anderson@...ux.dev>
Cc: netdev@...r.kernel.org, Andrew Lunn <andrew+netdev@...n.ch>,
"David S . Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Russell King <linux@...linux.org.uk>, upstream@...oha.com,
Kory Maincent <kory.maincent@...tlin.com>, Simon Horman <horms@...nel.org>,
Christian Marangi <ansuelsmth@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [net-next PATCH v4 06/11] net: phy: Export some functions
On 15.05.2025 04:57, Jakub Kicinski wrote:
> On Mon, 12 May 2025 12:10:08 -0400 Sean Anderson wrote:
>> Export a few functions so they can be used outside the phy subsystem:
>>
>> get_phy_c22_id is useful when probing MDIO devices which present a
>> phy-like interface despite not using the Linux ethernet phy subsystem.
>>
>> mdio_device_bus_match is useful when creating MDIO devices manually
>> (e.g. on non-devicetree platforms).
>>
>> At the moment the only (future) user of these functions selects PHYLIB,
>> so we do not need fallbacks for when CONFIG_PHYLIB=n.
>
The functions should only be exported once there is a user.
Therefore I'd suggest to remove this patch from the series.
> This one does not apply cleanly.
Powered by blists - more mailing lists