[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <54f2a7ff-640d-4a9d-bfc9-5190f295f466@lunn.ch>
Date: Thu, 27 Nov 2025 16:56:16 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Buday Csaba <buday.csaba@...lan.hu>
Cc: Jakub Kicinski <kuba@...nel.org>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 1/1] net: mdio: reset PHY before attempting to
access ID register
> c) what about using EXPORT_SYMBOL_FOR_MODULES() on the problematic
> functions? Are there any objections against it?
> This type of export is rarely used in the kernel, so I am uncertain
> about that. Is using it on functions declared in private headers
> also discouraged?
Rather than _FOR_MODULES, how about using a namespace.
https://docs.kernel.org/core-api/symbol-namespaces.html#how-to-use-symbols-exported-in-namespaces
Add a name space "NET_PHY_CORE_ONLY", and put these symbols into that
name space. We should notice any driver importing that namespace and
reject it.
Andrew
Powered by blists - more mailing lists