Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: richardcochran@gmail.com, ajay.kaher@broadcom.com,
	alexey.makhalov@broadcom.com, andrew+netdev@lunn.ch,
	bcm-kernel-feedback-list@broadcom.com, xiaoning.wang@nxp.com,
	davem@davemloft.net, dwmw2@infradead.org, edumazet@google.com,
	imx@lists.linux.dev, kuba@kernel.org, jonathan.lemon@gmail.com,
	netdev@vger.kernel.org, nick.shi@broadcom.com, pabeni@redhat.com,
	svens@linux.ibm.com, vadim.fedorenko@linux.dev,
	vladimir.oltean@nxp.com, wei.fang@nxp.com, yangbo.lu@nxp.com
Subject: Re: [PATCH net-next v2 0/2] ptp: safely cleanup when unregistering a PTP clock
Date: Wed, 17 Sep 2025 22:20:21 +0000	[thread overview]
Message-ID: <175814762198.2168096.17479042568343999293.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <aMnYIu7RbgfXrmGx@shell.armlinux.org.uk>

Hello:

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

On Tue, 16 Sep 2025 22:35:30 +0100 you wrote:
> (I'm assuming drivers/ptp/ patches go via net-next as there is no
> git tree against the "PTP HARDWARE CLOCK SUPPORT" maintainers entry.)
> 
> The standard rule in the kernel for unregistering user visible devices
> is to unpublish the userspace API before doing any shutdown of the
> resources necessary for the operation of the device.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] ptp: describe the two disables in ptp_set_pinfunc()
    https://git.kernel.org/netdev/net-next/c/0fcb1dc3e804
  - [net-next,v2,2/2] ptp: rework ptp_clock_unregister() to disable events
    https://git.kernel.org/netdev/net-next/c/a60fc3294a37

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-17 22:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16 21:35 [PATCH net-next v2 0/2] ptp: safely cleanup when unregistering a PTP clock Russell King (Oracle)
2025-09-16 21:35 ` [PATCH net-next v2 1/2] ptp: describe the two disables in ptp_set_pinfunc() Russell King (Oracle)
2025-09-16 21:36 ` [PATCH net-next v2 2/2] ptp: rework ptp_clock_unregister() to disable events Russell King (Oracle)
2025-09-17  8:38   ` Vladimir Oltean
2025-09-17 10:47   ` Vadim Fedorenko
2025-09-17 14:47 ` [PATCH net-next v2 0/2] ptp: safely cleanup when unregistering a PTP clock Richard Cochran
2025-09-17 22:20 ` 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=175814762198.2168096.17479042568343999293.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ajay.kaher@broadcom.com \
    --cc=alexey.makhalov@broadcom.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --cc=edumazet@google.com \
    --cc=imx@lists.linux.dev \
    --cc=jonathan.lemon@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=nick.shi@broadcom.com \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=svens@linux.ibm.com \
    --cc=vadim.fedorenko@linux.dev \
    --cc=vladimir.oltean@nxp.com \
    --cc=wei.fang@nxp.com \
    --cc=xiaoning.wang@nxp.com \
    --cc=yangbo.lu@nxp.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