Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Myeonghun Pak <mhun512@gmail.com>
Cc: richardcochran@gmail.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	ae878000@gmail.com
Subject: Re: [PATCH net v2] ptp: fc3: register PTP clock after initialization
Date: Thu, 06 Aug 2026 15:20:09 +0000	[thread overview]
Message-ID: <178602960938.1333975.3024284810821390320.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260803135942.48383-1-mhun512@gmail.com>

Hello:

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

On Mon,  3 Aug 2026 22:59:42 +0900 you wrote:
> ptp_clock_register() exposes the clock to userspace. If either following
> initialization operation fails, probe returns and devres frees idtfc3 while
> the registered clock still refers to the clock information embedded in it.
> 
> Complete the fallible initialization before registering the clock. Schedule
> the worker after registration because it requires the registered clock.
> This removes post-registration failures and avoids exposing a partially
> initialized clock.
> 
> [...]

Here is the summary with links:
  - [net,v2] ptp: fc3: register PTP clock after initialization
    https://git.kernel.org/netdev/net-next/c/762137ff748f

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



      reply	other threads:[~2026-08-06 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 13:59 [PATCH net v2] ptp: fc3: register PTP clock after initialization Myeonghun Pak
2026-08-06 15: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=178602960938.1333975.3024284810821390320.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ae878000@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhun512@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=stable@vger.kernel.org \
    /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