All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, Andrew Lunn <andrew+netdev@lunn.ch>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
	David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/2] net: phy: stop exporting phy_driver_register
Date: Sat, 20 Sep 2025 23:31:23 +0200	[thread overview]
Message-ID: <b86c2ecc-41f6-4f7f-85db-b7fa684d1fb7@gmail.com> (raw)

Once the last user of a clock in dp83640 has been removed, the clock should
be removed. So far orphaned clocks are cleaned up in dp83640_free_clocks()
only. Add the logic to remove orphaned clocks in dp83640_remove().
This allows to simplify the code, and use standard macro
module_phy_driver(). dp83640 was the last external user of
phy_driver_register(), so we can stop exporting this function afterwards.

Heiner Kallweit (2):
  net: phy: dp83640: improve phydev and driver removal handling
  net: phy: stop exporting phy_driver_register

 drivers/net/phy/dp83640.c    | 58 +++++++++++++-----------------------
 drivers/net/phy/phy_device.c |  4 +--
 include/linux/phy.h          |  1 -
 3 files changed, 22 insertions(+), 41 deletions(-)

-- 
2.51.0


             reply	other threads:[~2025-09-20 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-20 21:31 Heiner Kallweit [this message]
2025-09-20 21:33 ` [PATCH net-next 1/2] net: phy: dp83640: improve phydev and driver removal handling Heiner Kallweit
2025-09-22 15:47   ` Maxime Chevallier
2025-09-20 21:34 ` [PATCH net-next 2/2] net: phy: stop exporting phy_driver_register Heiner Kallweit
2025-09-24  0:10 ` [PATCH net-next 0/2] " patchwork-bot+netdevbpf

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=b86c2ecc-41f6-4f7f-85db-b7fa684d1fb7@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.