public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	andrew+netdev@lunn.ch, c-vankar@ti.com, danishanwar@ti.com,
	edumazet@google.com, kuba@kernel.org,
	martin.kaistra@linutronix.de, pabeni@redhat.com
Subject: Re: [PATCH v2 net-next] net: ethernet: ti: am65-cpsw: Use also port number to identify timestamps
Date: Tue, 10 Mar 2026 02:10:12 +0000	[thread overview]
Message-ID: <177310861229.2026004.10002739128726004925.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260306144439.cVwaaopR@linutronix.de>

Hello:

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

On Fri, 6 Mar 2026 15:44:39 +0100 you wrote:
> The driver uses packet-type (RX/TX) PTP-message type and PTP-sequence
> number to identify a matching timestamp packet for a skb. If the same
> PTP packet arrives on both ports (as in a PRP environment) then it is
> not obvious which event belongs to which skb.
> 
> The event contains also the port number on which it was received.
> Instead of masking it out, use it for matching.
> 
> [...]

Here is the summary with links:
  - [v2,net-next] net: ethernet: ti: am65-cpsw: Use also port number to identify timestamps
    https://git.kernel.org/netdev/net-next/c/a23c657e332f

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



      reply	other threads:[~2026-03-10  2:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 14:44 [PATCH v2 net-next] net: ethernet: ti: am65-cpsw: Use also port number to identify timestamps Sebastian Andrzej Siewior
2026-03-10  2: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=177310861229.2026004.10002739128726004925.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bigeasy@linutronix.de \
    --cc=c-vankar@ti.com \
    --cc=danishanwar@ti.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=martin.kaistra@linutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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