From: patchwork-bot+netdevbpf@kernel.org
To: Ravi Gunasekaran <r-gunasekaran@ti.com>
Cc: s-vadapalli@ti.com, rogerq@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
richardcochran@gmail.com, jreeder@ti.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, srk@ti.com, ed.trexel@hp.com
Subject: Re: [PATCH net v2] net: ethernet: ti: am65-cpts: Fix PTPv1 message type on TX packets
Date: Thu, 25 Apr 2024 15:30:34 +0000 [thread overview]
Message-ID: <171405903416.5824.618925777912040630.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240424071626.32558-1-r-gunasekaran@ti.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 24 Apr 2024 12:46:26 +0530 you wrote:
> From: Jason Reeder <jreeder@ti.com>
>
> The CPTS, by design, captures the messageType (Sync, Delay_Req, etc.)
> field from the second nibble of the PTP header which is defined in the
> PTPv2 (1588-2008) specification. In the PTPv1 (1588-2002) specification
> the first two bytes of the PTP header are defined as the versionType
> which is always 0x0001. This means that any PTPv1 packets that are
> tagged for TX timestamping by the CPTS will have their messageType set
> to 0x0 which corresponds to a Sync message type. This causes issues
> when a PTPv1 stack is expecting a Delay_Req (messageType: 0x1)
> timestamp that never appears.
>
> [...]
Here is the summary with links:
- [net,v2] net: ethernet: ti: am65-cpts: Fix PTPv1 message type on TX packets
https://git.kernel.org/netdev/net/c/1b9e743e923b
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:[~2024-04-25 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 7:16 [PATCH net v2] net: ethernet: ti: am65-cpts: Fix PTPv1 message type on TX packets Ravi Gunasekaran
2024-04-25 1:36 ` Trexel, Ed
2024-04-25 5:09 ` Ravi Gunasekaran
2024-04-25 15: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=171405903416.5824.618925777912040630.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=ed.trexel@hp.com \
--cc=edumazet@google.com \
--cc=jreeder@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=r-gunasekaran@ti.com \
--cc=richardcochran@gmail.com \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.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 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.