From: Anoob Joseph <anoobj@marvell.com>
To: Archana Muniganti <marchana@marvell.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
Ankur Dwivedi <adwivedi@marvell.com>
Cc: Archana Muniganti <marchana@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] common/cpt: add check for mac_len
Date: Wed, 16 Sep 2020 15:56:59 +0000 [thread overview]
Message-ID: <CY4PR18MB1157D7E42801DD6D56739815DF210@CY4PR18MB1157.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1600252620-18201-2-git-send-email-marchana@marvell.com>
>
> HMAC/HASH opcode algorithms supports fixed mac length.
> Allowed session creation to fail when requested for unsupported MAC
> length for HMAC/HASH-only use cases.
>
> Signed-off-by: Archana Muniganti <marchana@marvell.com>
Series Acked-by: Anoob Joseph <anoobj@marvell.com>
next prev parent reply other threads:[~2020-09-16 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 10:36 [dpdk-dev] [PATCH 1/2] common/cpt: remove redundant CPT_BYTE_* macros Archana Muniganti
2020-09-16 10:37 ` [dpdk-dev] [PATCH 2/2] common/cpt: add check for mac_len Archana Muniganti
2020-09-16 15:56 ` Anoob Joseph [this message]
2020-10-09 12:26 ` [dpdk-dev] [PATCH 1/2] common/cpt: remove redundant CPT_BYTE_* macros Akhil Goyal
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=CY4PR18MB1157D7E42801DD6D56739815DF210@CY4PR18MB1157.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=adwivedi@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=marchana@marvell.com \
--cc=stable@dpdk.org \
/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).