From: Akhil Goyal <gakhil@marvell.com>
To: Vamsi Krishna Attunuru <vattunuru@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Vamsi Krishna Attunuru <vattunuru@marvell.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"mdr@ashroe.eu" <mdr@ashroe.eu>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"rasland@nvidia.com" <rasland@nvidia.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: RE: [PATCH 1/1] doc: notice to add new ipsec event subtypes
Date: Fri, 24 Jun 2022 18:18:44 +0000 [thread overview]
Message-ID: <CO6PR18MB44845915DB20FD7CC34CF32CD8B49@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220624133551.365962-1-vattunuru@marvell.com>
> Subject: [PATCH 1/1] doc: notice to add new ipsec event subtypes
Title should be
doc: announce addition of new IPsec event subtypes
>
> Based on discussion in below email thread, the new event subtypes can be
> added in 22.11 release with fixing any compatability issues mentioned in
> the mail thread.
>
> https://patches.dpdk.org/project/dpdk/patch/20220416192530.173895-8-
> gakhil@marvell.com/
>
Description should be
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.
You can give the reference to patch after --- so that it is not visible in git log
Adding more people for acks.
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
Other that this
Acked-by: Akhil Goyal <gakhil@marvell.com>
next prev parent reply other threads:[~2022-06-24 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 13:35 Vamsi Attunuru
2022-06-24 18:18 ` Akhil Goyal [this message]
2022-06-27 5:29 ` [PATCH v2 1/1] doc: announce addition of " Vamsi Attunuru
2022-07-06 9:49 ` Zhang, Roy Fan
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=CO6PR18MB44845915DB20FD7CC34CF32CD8B49@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mdr@ashroe.eu \
--cc=rasland@nvidia.com \
--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).