From: patchwork-bot+netdevbpf@kernel.org
To: Jaakko Karrenpalo <jkarrenpalo@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, lukma@denx.de,
danishanwar@ti.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, jaakko.karrenpalo@fi.abb.com
Subject: Re: [PATCH net-next v5 1/2] net: hsr: Fix PRP duplicate detection
Date: Thu, 13 Mar 2025 09:10:31 +0000 [thread overview]
Message-ID: <174185703151.1429089.2609915440433939062.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250307161700.1045-1-jkarrenpalo@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 7 Mar 2025 18:16:59 +0200 you wrote:
> Add PRP specific function for handling duplicate
> packets. This is needed because of potential
> L2 802.1p prioritization done by network switches.
>
> The L2 prioritization can re-order the PRP packets
> from a node causing the existing implementation to
> discard the frame(s) that have been received 'late'
> because the sequence number is before the previous
> received packet. This can happen if the node is
> sending multiple frames back-to-back with different
> priority.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] net: hsr: Fix PRP duplicate detection
https://git.kernel.org/netdev/net-next/c/05fd00e5e7b1
- [net-next,v5,2/2] net: hsr: Add KUnit test for PRP
https://git.kernel.org/netdev/net-next/c/814dbf4b6c95
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:[~2025-03-13 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 16:16 [PATCH net-next v5 1/2] net: hsr: Fix PRP duplicate detection Jaakko Karrenpalo
2025-03-07 16:17 ` [PATCH net-next v5 2/2] net: hsr: Add KUnit test for PRP Jaakko Karrenpalo
2025-03-13 9: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=174185703151.1429089.2609915440433939062.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jaakko.karrenpalo@fi.abb.com \
--cc=jkarrenpalo@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukma@denx.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