From: Akhil Goyal <gakhil@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Ankur Dwivedi <adwivedi@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Vamsi Krishna Attunuru <vattunuru@marvell.com>
Subject: RE: [PATCH v2 0/3] MACsec capability verification
Date: Tue, 19 Sep 2023 19:17:40 +0000 [thread overview]
Message-ID: <CO6PR18MB44844C0AD6F4C82C50CE76C5D8FAA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230919135409.2544309-1-gakhil@marvell.com>
> Subject: [PATCH v2 0/3] MACsec capability verification
>
> Changes in v2: Fixed clang build issue in 3/3 patch.
>
> Ankur Dwivedi (3):
> security: add MACsec algo in capability index
> net/cnxk: add MACsec capability
> test/security: add capability verification for MACsec
>
> app/test/test_security_inline_macsec.c | 373 ++++++++++++++++++++-----
> drivers/common/cnxk/roc_features.h | 6 +
> drivers/common/cnxk/roc_mcs.h | 3 +
> drivers/net/cnxk/cn10k_ethdev_sec.c | 120 +++++++-
> lib/security/rte_security.c | 4 +
> lib/security/rte_security.h | 3 +
> 6 files changed, 428 insertions(+), 81 deletions(-)
>
Series Applied to dpdk-next-crypto
prev parent reply other threads:[~2023-09-19 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 3:44 [PATCH 1/3] security: add MACsec algo in capability index Akhil Goyal
2023-07-31 3:44 ` [PATCH 2/3] net/cnxk: add MACsec capability Akhil Goyal
2023-07-31 3:44 ` [PATCH 3/3] test/security: add capability verification for MACsec Akhil Goyal
2023-09-19 13:54 ` [PATCH v2 0/3] MACsec capability verification Akhil Goyal
2023-09-19 13:54 ` [PATCH v2 1/3] security: add MACsec algo in capability index Akhil Goyal
2023-09-19 13:54 ` [PATCH v2 2/3] net/cnxk: add MACsec capability Akhil Goyal
2023-09-19 13:54 ` [PATCH v2 3/3] test/security: add capability verification for MACsec Akhil Goyal
2023-09-19 19:17 ` Akhil Goyal [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=CO6PR18MB44844C0AD6F4C82C50CE76C5D8FAA@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=adwivedi@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=vattunuru@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).