All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Miroslav Lichvar <mlichvar@redhat.com>
Cc: netdev@vger.kernel.org, richardcochran@gmail.com,
	tglx@linutronix.de, jstultz@google.com, arnd@arndb.de
Subject: Re: [PATCH v2 net-next] ptp: Limit time setting of PTP clocks
Date: Mon, 01 Sep 2025 20:10:10 +0000	[thread overview]
Message-ID: <175675741099.3870710.1056034775487131143.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250828103300.1387025-1-mlichvar@redhat.com>

Hello:

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

On Thu, 28 Aug 2025 12:32:53 +0200 you wrote:
> Networking drivers implementing PTP clocks and kernel socket code
> handling hardware timestamps use the 64-bit signed ktime_t type counting
> nanoseconds. When a PTP clock reaches the maximum value in year 2262,
> the timestamps returned to applications will overflow into year 1667.
> The same thing happens when injecting a large offset with
> clock_adjtime(ADJ_SETOFFSET).
> 
> [...]

Here is the summary with links:
  - [v2,net-next] ptp: Limit time setting of PTP clocks
    https://git.kernel.org/netdev/net-next/c/5a8c02a6bf52

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



      parent reply	other threads:[~2025-09-01 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-28 10:32 [PATCH v2 net-next] ptp: Limit time setting of PTP clocks Miroslav Lichvar
2025-08-28 12:53 ` Vadim Fedorenko
2025-09-01 20:10 ` 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=175675741099.3870710.1056034775487131143.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=arnd@arndb.de \
    --cc=jstultz@google.com \
    --cc=mlichvar@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.