From: Akhil Goyal <gakhil@marvell.com>
To: Anoob Joseph <anoobj@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
Archana Muniganti <marchana@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] security: fix comments
Date: Thu, 28 Apr 2022 07:28:37 +0000 [thread overview]
Message-ID: <CO6PR18MB4484D3464A164983673B70E2D8FD9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1651039306-149-1-git-send-email-anoobj@marvell.com>
> Subject: [PATCH] security: fix comments
>
> Fix comments to reflect the field.
>
> Fixes: ad7515a39f2a ("security: add SA lifetime configuration")
> Cc: anoobj@marvell.com
>
> Reported-by: Thomas Monjalon <thomas@monjalon.net>
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
Applied to dpdk-next-crypto
Cc: stable@dpdk.org
parent reply other threads:[~2022-04-28 7:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1651039306-149-1-git-send-email-anoobj@marvell.com>]
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=CO6PR18MB4484D3464A164983673B70E2D8FD9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=ktejasree@marvell.com \
--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).