From: patchwork-bot+netdevbpf@kernel.org
To: Radu Pirea (NXP OSS) <radu-nicolae.pirea@oss.nxp.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, sgoutham@marvell.com,
gakula@marvell.com, sbhatta@marvell.com, hkelam@marvell.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, borisp@nvidia.com, saeedm@nvidia.com,
leon@kernel.org, sd@queasysnail.net, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk,
richardcochran@gmail.com, sebastian.tobuschat@oss.nxp.com,
phaddad@nvidia.com, ehakim@nvidia.com, raeds@nvidia.com,
atenart@kernel.org
Subject: Re: [PATCH net v7 0/4] Add update_pn flag
Date: Tue, 10 Oct 2023 08:50:26 +0000 [thread overview]
Message-ID: <169692782642.27521.12623155757527966309.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231005180636.672791-1-radu-nicolae.pirea@oss.nxp.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 5 Oct 2023 21:06:32 +0300 you wrote:
> Patches extracted from
> https://lore.kernel.org/all/20230928084430.1882670-1-radu-nicolae.pirea@oss.nxp.com/
> Update_pn flag will let the offloaded MACsec implementations to know when
> the PN is updated.
>
> Radu P.
>
> [...]
Here is the summary with links:
- [net,v7,1/4] net: macsec: indicate next pn update when offloading
https://git.kernel.org/netdev/net/c/0412cc846a1e
- [net,v7,2/4] octeontx2-pf: mcs: update PN only when update_pn is true
https://git.kernel.org/netdev/net/c/4dcf38ae3ca1
- [net,v7,3/4] net: phy: mscc: macsec: reject PN update requests
https://git.kernel.org/netdev/net/c/e0a8c918daa5
- [net,v7,4/4] net/mlx5e: macsec: use update_pn flag instead of PN comparation
https://git.kernel.org/netdev/net/c/fde2f2d7f23d
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:[~2023-10-10 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 18:06 [PATCH net v7 0/4] Add update_pn flag Radu Pirea (NXP OSS)
2023-10-05 18:06 ` [PATCH net v7 1/4] net: macsec: indicate next pn update when offloading Radu Pirea (NXP OSS)
2023-10-05 18:06 ` [PATCH net v7 2/4] octeontx2-pf: mcs: update PN only when update_pn is true Radu Pirea (NXP OSS)
2023-10-05 18:06 ` [PATCH net v7 3/4] net: phy: mscc: macsec: reject PN update requests Radu Pirea (NXP OSS)
2023-10-05 18:06 ` [PATCH net v7 4/4] net/mlx5e: macsec: use update_pn flag instead of PN comparation Radu Pirea (NXP OSS)
2023-10-10 8:09 ` [PATCH net v7 0/4] Add update_pn flag Sabrina Dubroca
2023-10-10 8:50 ` 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=169692782642.27521.12623155757527966309.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ehakim@nvidia.com \
--cc=gakula@marvell.com \
--cc=hkallweit1@gmail.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phaddad@nvidia.com \
--cc=radu-nicolae.pirea@oss.nxp.com \
--cc=raeds@nvidia.com \
--cc=richardcochran@gmail.com \
--cc=saeedm@nvidia.com \
--cc=sbhatta@marvell.com \
--cc=sd@queasysnail.net \
--cc=sebastian.tobuschat@oss.nxp.com \
--cc=sgoutham@marvell.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;
as well as URLs for NNTP newsgroup(s).