mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Buday Csaba <buday.csaba@prolan.hu>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/1] net: mdio: reset PHY before attempting to access ID register
Date: Thu, 27 Nov 2025 16:56:16 +0100	[thread overview]
Message-ID: <54f2a7ff-640d-4a9d-bfc9-5190f295f466@lunn.ch> (raw)
In-Reply-To: <aSgzRMf1LZycQoni@debianbuilder>

> 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

  reply	other threads:[~2025-11-27 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 11:15 Buday Csaba
2025-11-26  2:43 ` Jakub Kicinski
2025-11-26  7:03   ` Buday Csaba
2025-11-27 11:17   ` Buday Csaba
2025-11-27 15:56     ` Andrew Lunn [this message]
2025-11-26 15:17 ` kernel test robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54f2a7ff-640d-4a9d-bfc9-5190f295f466@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=buday.csaba@prolan.hu \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®