From: patchwork-bot+netdevbpf@kernel•org
To: Joshua Washington <joshwash@google•com>
Cc: netdev@vger•kernel.org, thostet@google•com, richardcochran@gmail•com
Subject: Re: [PATCH net 0/2] gve: Fix NULL dereferencing with PTP clock
Date: Fri, 31 Oct 2025 23:30:09 +0000 [thread overview]
Message-ID: <176195340950.666625.9872917114678524497.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251029184555.3852952-1-joshwash@google.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Wed, 29 Oct 2025 11:45:38 -0700 you wrote:
> From: Tim Hostetler <thostet@google•com>
>
> This patch series fixes NULL dereferences that are possible with gve's
> PTP clock due to not stubbing certain ptp_clock_info callbacks.
>
> Tim Hostetler (2):
> gve: Implement gettimex64 with -EOPNOTSUPP
> gve: Implement settime64 with -EOPNOTSUPP
>
> [...]
Here is the summary with links:
- [net,1/2] gve: Implement gettimex64 with -EOPNOTSUPP
https://git.kernel.org/netdev/net/c/6ab753b5d8e5
- [net,2/2] gve: Implement settime64 with -EOPNOTSUPP
https://git.kernel.org/netdev/net/c/329d050bbe63
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-10-31 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 18:45 [PATCH net 0/2] gve: Fix NULL dereferencing with PTP clock Joshua Washington
2025-10-29 18:45 ` [PATCH net 1/2] gve: Implement gettimex64 with -EOPNOTSUPP Joshua Washington
2025-10-29 18:45 ` [PATCH net 2/2] gve: Implement settime64 " Joshua Washington
2025-10-30 9:43 ` [PATCH net 0/2] gve: Fix NULL dereferencing with PTP clock Simon Horman
2025-10-30 9:48 ` Simon Horman
2025-10-30 17:01 ` Tim Hostetler
2025-10-31 23:30 ` 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=176195340950.666625.9872917114678524497.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=joshwash@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=richardcochran@gmail$(echo .)com \
--cc=thostet@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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