From: patchwork-bot+netdevbpf@kernel.org
To: Harshitha Ramamurthy <hramamurthy@google.com>
Cc: netdev@vger.kernel.org, joshwash@google.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
jstultz@google.com, tglx@kernel.org, sboyd@kernel.org,
willemb@google.com, nktgrg@google.com, jfraker@google.com,
ziweixiao@google.com, maolson@google.com, jordanrhee@google.com,
thostet@google.com, alok.a.tiwari@oracle.com,
pkaligineedi@google.com, horms@kernel.org, dwmw2@infradead.org,
jacob.e.keller@intel.com, yyd@google.com, jefrogers@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v8 0/3] gve: add support for PTP gettimex64
Date: Wed, 20 May 2026 01:30:18 +0000 [thread overview]
Message-ID: <177924061888.2943546.1863313939074098294.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260514225842.110706-1-hramamurthy@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 14 May 2026 22:58:39 +0000 you wrote:
> From: Jordan Rhee <jordanrhee@google.com>
>
> This patch series adds support to obtain near-simultaneous NIC and
> system timestamps with gettimex64. This enables daemons like
> chrony and phc2sys to synchronize the system clock to the NIC clock.
>
> GVE does not have direct register access to the NIC hardware clock, so
> it must issue an AdminQ command to read the NIC clock. Two paths
> for obtaining a cross-timestamp are implemented: a precise path using
> system counter values sampled by the device, and a fallback path using
> system counter values sampled in the driver using
> ptp_read_system_prets()/postts().
>
> [...]
Here is the summary with links:
- [net-next,v8,1/3] gve: skip error logging for retryable AdminQ commands
https://git.kernel.org/netdev/net-next/c/55687124a86f
- [net-next,v8,2/3] gve: make nic clock reads thread safe
https://git.kernel.org/netdev/net-next/c/4bbcd7e24aaa
- [net-next,v8,3/3] gve: implement PTP gettimex64
https://git.kernel.org/netdev/net-next/c/22b2aae747f7
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:[~2026-05-20 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 22:58 [PATCH net-next v8 0/3] gve: add support for PTP gettimex64 Harshitha Ramamurthy
2026-05-14 22:58 ` [PATCH net-next v8 1/3] gve: skip error logging for retryable AdminQ commands Harshitha Ramamurthy
2026-05-14 22:58 ` [PATCH net-next v8 2/3] gve: make nic clock reads thread safe Harshitha Ramamurthy
2026-05-14 22:58 ` [PATCH net-next v8 3/3] gve: implement PTP gettimex64 Harshitha Ramamurthy
2026-05-20 1: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=177924061888.2943546.1863313939074098294.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jefrogers@google.com \
--cc=jfraker@google.com \
--cc=jordanrhee@google.com \
--cc=joshwash@google.com \
--cc=jstultz@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maolson@google.com \
--cc=netdev@vger.kernel.org \
--cc=nktgrg@google.com \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=richardcochran@gmail.com \
--cc=sboyd@kernel.org \
--cc=tglx@kernel.org \
--cc=thostet@google.com \
--cc=willemb@google.com \
--cc=yyd@google.com \
--cc=ziweixiao@google.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