From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: Vamsi Attunuru <vattunuru@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "jerinj@marvell.com" <jerinj@marvell.com>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"mdr@ashroe.eu" <mdr@ashroe.eu>
Subject: RE: [PATCH v2 1/1] doc: announce addition of new ipsec event subtypes
Date: Wed, 6 Jul 2022 09:49:11 +0000 [thread overview]
Message-ID: <MW5PR11MB58090D9E50079F816F346632B8809@MW5PR11MB5809.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220627052937.759050-1-vattunuru@marvell.com>
> -----Original Message-----
> From: Vamsi Attunuru <vattunuru@marvell.com>
> Sent: Monday, June 27, 2022 6:30 AM
> To: dev@dpdk.org
> Cc: jerinj@marvell.com; vattunuru@marvell.com; gakhil@marvell.com;
> ferruh.yigit@intel.com; thomas@monjalon.net; anoobj@marvell.com;
> mdr@ashroe.eu
> Subject: [PATCH v2 1/1] doc: announce addition of new ipsec event subtypes
>
> New event subtypes need to be added for notifying expiry events
> upon reaching IPsec SA soft packet expiry and hard packet/byte
> expiry limits. This would be added in DPDK 22.11.
>
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
> Acked-by: Akhil Goyal <gakhil@marvell.com>
> ---
> More details on new event subtype proposal discussion are in below email
> thread.
> https://patches.dpdk.org/project/dpdk/patch/20220416192530.173895-8-
> gakhil@marvell.com/
>
> v2: rephrase title and git log.
> ---
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2022-07-06 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 13:35 [PATCH 1/1] doc: notice to add " Vamsi Attunuru
2022-06-24 18:18 ` Akhil Goyal
2022-06-27 5:29 ` [PATCH v2 1/1] doc: announce addition of " Vamsi Attunuru
2022-07-06 9:49 ` Zhang, Roy Fan [this message]
2022-07-11 14:53 ` Jerin Jacob
2022-07-12 11:44 ` Andrew Rybchenko
2022-07-17 10:07 ` Thomas Monjalon
2022-07-12 15:03 ` Thomas Monjalon
2022-07-12 15:30 ` [EXT] " Akhil Goyal
2022-07-12 20:44 ` Thomas Monjalon
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=MW5PR11MB58090D9E50079F816F346632B8809@MW5PR11MB5809.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=thomas@monjalon.net \
--cc=vattunuru@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).