From: Akhil Goyal <gakhil@marvell.com>
To: Nithinsen Kaithakadan <nkaithakadan@marvell.com>,
Radu Nicolau <radu.nicolau@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] examples/ipsec-secgw: fix iv len in ctr 192/256
Date: Sun, 2 Mar 2025 20:27:12 +0000 [thread overview]
Message-ID: <CO6PR18MB448465454D99773C13731427D8CE2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250207134545.63820-1-nkaithakadan@marvell.com>
> -----Original Message-----
> From: Nithinsen Kaithakadan <nkaithakadan@marvell.com>
> Sent: Friday, February 7, 2025 7:16 PM
> To: Radu Nicolau <radu.nicolau@intel.com>; Akhil Goyal <gakhil@marvell.com>
> Cc: Anoob Joseph <anoobj@marvell.com>; Tejasree Kondoj
> <ktejasree@marvell.com>; Nithin Kumar Dabilpuram
> <ndabilpuram@marvell.com>; dev@dpdk.org
> Subject: [PATCH] examples/ipsec-secgw: fix iv len in ctr 192/256
>
> This patch fixes IV length to 8 in case of AES-CTR 192/256.
>
> Fixes: 9413c3901f31 ("examples/ipsec-secgw: support additional algorithms")
>
> Signed-off-by: Nithinsen Kaithakadan <nkaithakadan@marvell.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>
Updated .mailmap
Applied to dpdk-next-crypto
next prev parent reply other threads:[~2025-03-02 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 13:45 Nithinsen Kaithakadan
2025-02-10 8:07 ` Anoob Joseph
2025-02-11 12:21 ` Nithinsen Kaithakadan
2025-03-02 20:27 ` Akhil Goyal [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-07 13:18 Nithinsen Kaithakadan
2025-02-10 3:11 ` Anoob Joseph
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=CO6PR18MB448465454D99773C13731427D8CE2@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=ktejasree@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=nkaithakadan@marvell.com \
--cc=radu.nicolau@intel.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).