All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: andrew@lunn.ch, andrew+netdev@lunn.ch, linux@armlinux.org.uk,
	edumazet@google.com, pabeni@redhat.com, kuba@kernel.org,
	davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: phy: stop exporting phy_driver_register
Date: Wed, 24 Sep 2025 00:10:09 +0000	[thread overview]
Message-ID: <175867260900.1969801.17701597899099018236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <b86c2ecc-41f6-4f7f-85db-b7fa684d1fb7@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sat, 20 Sep 2025 23:31:23 +0200 you wrote:
> 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.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] net: phy: dp83640: improve phydev and driver removal handling
    https://git.kernel.org/netdev/net-next/c/42e2a9e11a1d
  - [net-next,2/2] net: phy: stop exporting phy_driver_register
    https://git.kernel.org/netdev/net-next/c/092263a03105

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-09-24  0:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-20 21:31 [PATCH net-next 0/2] net: phy: stop exporting phy_driver_register Heiner Kallweit
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 ` patchwork-bot+netdevbpf [this message]

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=175867260900.1969801.17701597899099018236.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.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.