From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Anoob Joseph" <anoobj@marvell.com>,
"Akhil Goyal" <gakhil@marvell.com>,
"Jerin Jacob" <jerinj@marvell.com>
Cc: "Archana Muniganti" <marchana@marvell.com>,
"Tejasree Kondoj" <ktejasree@marvell.com>, <dev@dpdk.org>
Subject: RE: [PATCH] security: fix comments
Date: Wed, 27 Apr 2022 10:20:52 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87007@smartserver.smartshare.dk> (raw)
In-Reply-To: <1651039306-149-1-git-send-email-anoobj@marvell.com>
> From: Anoob Joseph [mailto:anoobj@marvell.com]
> Sent: Wednesday, 27 April 2022 08.02
>
> 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>
> ---
> lib/security/rte_security.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/security/rte_security.h b/lib/security/rte_security.h
> index 2a43cbe..675db94 100644
> --- a/lib/security/rte_security.h
> +++ b/lib/security/rte_security.h
> @@ -311,9 +311,9 @@ struct rte_security_ipsec_lifetime {
> uint64_t bytes_soft_limit;
> /**< Soft expiry limit in bytes */
> uint64_t packets_hard_limit;
> - /**< Soft expiry limit in number of packets */
> + /**< Hard expiry limit in number of packets */
> uint64_t bytes_hard_limit;
> - /**< Soft expiry limit in bytes */
> + /**< Hard expiry limit in bytes */
> };
>
> /**
> --
> 2.7.4
>
Reviewed-by: Morten Brørup <mb@smartsharesystems.com>
next prev parent reply other threads:[~2022-04-27 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 6:01 Anoob Joseph
2022-04-27 8:20 ` Morten Brørup [this message]
2022-04-28 7:28 ` 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=98CBD80474FA8B44BF855DF32C47DC35D87007@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=ktejasree@marvell.com \
--cc=marchana@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).