From: patchwork-bot+netdevbpf@kernel.org
To: Tim Hostetler <thostet@google.com>
Cc: netdev@vger.kernel.org, richardcochran@gmail.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
kuniyu@google.com, hramamurthy@google.com,
vadim.fedorenko@linux.dev
Subject: Re: [PATCH net-next v2] ptp: Return -EINVAL on ptp_clock_register if required ops are NULL
Date: Thu, 06 Nov 2025 02:00:32 +0000 [thread overview]
Message-ID: <176239443274.3831359.3134439998474183740.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251104225915.2040080-1-thostet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 4 Nov 2025 14:59:15 -0800 you wrote:
> ptp_clock should never be registered unless it stubs one of gettimex64()
> or gettime64() and settime64(). WARN_ON_ONCE and error out if either set
> of function pointers is null.
>
> For consistency, n_alarm validation is also folded into the
> WARN_ON_ONCE.
>
> [...]
Here is the summary with links:
- [net-next,v2] ptp: Return -EINVAL on ptp_clock_register if required ops are NULL
https://git.kernel.org/netdev/net-next/c/dfb073d32cac
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-11-06 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 22:59 [PATCH net-next v2] ptp: Return -EINVAL on ptp_clock_register if required ops are NULL Tim Hostetler
2025-11-05 12:26 ` Richard Cochran
2025-11-06 2:00 ` patchwork-bot+netdevbpf [this message]
2025-11-08 4:48 ` Nathan Chancellor
2025-11-08 4:59 ` Kuniyuki Iwashima
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=176239443274.3831359.3134439998474183740.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=thostet@google.com \
--cc=vadim.fedorenko@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).