From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerinjacobk@gmail.com>,
Vamsi Attunuru <vattunuru@marvell.com>
Cc: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
dev@dpdk.org, "dev@dpdk.org" <dev@dpdk.org>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"mdr@ashroe.eu" <mdr@ashroe.eu>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [PATCH v2 1/1] doc: announce addition of new ipsec event subtypes
Date: Sun, 17 Jul 2022 12:07:01 +0200 [thread overview]
Message-ID: <1909614.yKVeVyVuyW@thomas> (raw)
In-Reply-To: <26350d32-1a76-e56d-6875-d0aa4141541c@oktetlabs.ru>
> >>> 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>
> >> Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
> > Acked-by: Jerin Jacob <jerinj@marvell.com>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Applied, thanks.
next prev parent reply other threads:[~2022-07-17 10:07 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
2022-07-11 14:53 ` Jerin Jacob
2022-07-12 11:44 ` Andrew Rybchenko
2022-07-17 10:07 ` Thomas Monjalon [this message]
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=1909614.yKVeVyVuyW@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=mdr@ashroe.eu \
--cc=roy.fan.zhang@intel.com \
--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).