From: Akhil Goyal <gakhil@marvell.com>
To: Anoob Joseph <anoobj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "radu.nicolau@intel.com" <radu.nicolau@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"abhijits.sinha@intel.com" <abhijits.sinha@intel.com>,
"daniel.m.buckley@intel.com" <daniel.m.buckley@intel.com>,
Archana Muniganti <marchana@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"matan@nvidia.com" <matan@nvidia.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce SA config option struct changes
Date: Mon, 2 Aug 2021 12:41:37 +0000 [thread overview]
Message-ID: <CO6PR18MB4484B644B2CC70B1EF2DA0F0D8EF9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <PH0PR18MB46720DF67DA3722EE4F3FF24DFEF9@PH0PR18MB4672.namprd18.prod.outlook.com>
> Hi Akhil,
>
> There are 2 more items that I would like to add.
> - IV gen (in ``rte_security_ipsec_sa_options``)
> - SA lifetime configuration (in ``rte_security_ipsec_xform``)
>
> http://patches.dpdk.org/project/dpdk/patch/1626759974-334-2-git-send-
> email-anoobj@marvell.com/
> http://patches.dpdk.org/project/dpdk/patch/1626759974-334-3-git-send-
> email-anoobj@marvell.com/
>
> Do you recommend sending separate deprecation notice or can this patch be
> updated to cover those as well?
>
> Thanks,
> Anoob
>
This patch is to cover changes in ``rte_security_ipsec_sa_options``, hence for iv_gen no need.
For ipsec_xform a new one would be good.
next prev parent reply other threads:[~2021-08-02 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 17:44 Akhil Goyal
2021-08-02 9:43 ` Anoob Joseph
2021-08-02 12:41 ` Akhil Goyal [this message]
2021-08-04 17:03 ` Akhil Goyal
2021-08-05 10:00 ` Nicolau, Radu
2021-08-05 10:14 ` Hemant Agrawal
2021-08-07 13:31 ` Jerin Jacob
2021-08-07 17:17 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2021-06-30 11:20 Archana Muniganti
2021-07-31 17:53 ` 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=CO6PR18MB4484B644B2CC70B1EF2DA0F0D8EF9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=abhijits.sinha@intel.com \
--cc=anoobj@marvell.com \
--cc=daniel.m.buckley@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktejasree@marvell.com \
--cc=marchana@marvell.com \
--cc=matan@nvidia.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).