From: patchwork-bot+netdevbpf@kernel.org
To: Emeel Hakim <ehakim@nvidia.com>
Cc: dsahern@kernel.org, sd@queasysnail.net, netdev@vger.kernel.org,
raeds@nvidia.com, tariqt@nvidia.com
Subject: Re: [PATCH main v5 1/2] macsec: add Extended Packet Number support
Date: Fri, 16 Sep 2022 16:40:14 +0000 [thread overview]
Message-ID: <166334641480.16685.6458039498402066702.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220911092656.13986-1-ehakim@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Sun, 11 Sep 2022 12:26:55 +0300 you wrote:
> This patch adds support for extended packet number (XPN).
> XPN can be configured by passing 'cipher gcm-aes-xpn-128' as part of
> the ip link add command using macsec type.
> In addition, using 'xpn' keyword instead of the 'pn', passing a 12
> bytes salt using the 'salt' keyword and passing short secure channel
> id (ssci) using the 'ssci' keyword as part of the ip macsec command
> is required (see example).
>
> [...]
Here is the summary with links:
- [main,v5,1/2] macsec: add Extended Packet Number support
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=6ce23b7c2d79
- [main,v5,2/2] macsec: add user manual description for extended packet number feature
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=319c643ed741
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:[~2022-09-16 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 9:26 [PATCH main v5 1/2] macsec: add Extended Packet Number support Emeel Hakim
2022-09-11 9:26 ` [PATCH main v5 2/2] macsec: add user manual description for extended packet number feature Emeel Hakim
2022-09-11 21:22 ` Sabrina Dubroca
2022-09-11 21:20 ` [PATCH main v5 1/2] macsec: add Extended Packet Number support Sabrina Dubroca
2022-09-16 16:40 ` 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=166334641480.16685.6458039498402066702.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=ehakim@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=raeds@nvidia.com \
--cc=sd@queasysnail.net \
--cc=tariqt@nvidia.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).