From: patchwork-bot+netdevbpf@kernel.org
To: James Hilliard <james.hilliard1@gmail.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
richardcochran@gmail.com, andrew+netdev@lunn.ch,
yangbo.lu@nxp.com, mlichvar@redhat.com, edumazet@kernel.org,
davem@davemloft.net, linux-kernel@vger.kernel.org,
vadim.fedorenko@linux.dev
Subject: Re: [PATCH net v6 0/5] ptp: make virtual clock sampling and teardown failure-safe
Date: Fri, 30 Oct 2026 23:20:17 +0000 [thread overview]
Message-ID: <179340241708.1826218.11378651277022206414.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026-ptp-vclock-sampling-v6-0-e705612541f1@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 26 Oct 2026 12:11:26 -0600 you wrote:
> Fix virtual-clock sampling errors, registration rollback and parent
> teardown in separate patches. Keep failed PHC reads out of the timecounter
> and serialize extended samples with virtual-clock adjustments. Also
> preserve the zero sentinel for packets without hardware timestamps.
>
> Retain the existing cyclecounter mask, scaling and conversion windows.
> Retry the first failed refresh promptly, then back off consecutive failures
> while preserving regular two-second refresh attempts. Queue the first
> refresh immediately after registration. Prolonged sampling gaps remain
> subject to the existing half-wrap conversion window and full-wrap sampling
> limit.
>
> [...]
Here is the summary with links:
- [net,v6,1/5] ptp: drain virtual clock sysfs operations before unregistering children
https://git.kernel.org/netdev/net/c/0e4a135aebc7
- [net,v6,2/5] ptp: unwind partially completed virtual clock creation
https://git.kernel.org/netdev/net/c/3dea778260e3
- [net,v6,3/5] ptp: vclock: propagate physical clock sampling errors
https://git.kernel.org/netdev/net/c/d1bdfdafd663
- [net,v6,4/5] ptp: vclock: serialize extended samples with counter updates
https://git.kernel.org/netdev/net/c/d3fcce5afe3b
- [net,v6,5/5] ptp: vclock: preserve missing hardware timestamps
https://git.kernel.org/netdev/net/c/63787dfd1b5a
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-10-30 23:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 18:11 James Hilliard
2026-10-26 18:11 ` [PATCH net v6 1/5] ptp: drain virtual clock sysfs operations before unregistering children James Hilliard
2026-10-26 18:11 ` [PATCH net v6 2/5] ptp: unwind partially completed virtual clock creation James Hilliard
2026-10-26 18:11 ` [PATCH net v6 3/5] ptp: vclock: propagate physical clock sampling errors James Hilliard
2026-10-26 18:11 ` [PATCH net v6 4/5] ptp: vclock: serialize extended samples with counter updates James Hilliard
2026-10-26 18:11 ` [PATCH net v6 5/5] ptp: vclock: preserve missing hardware timestamps James Hilliard
2026-10-30 23: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=179340241708.1826218.11378651277022206414.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=james.hilliard1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
--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
all inboxes | Powered by JetHome®