From: Akhil Goyal <akhil.goyal@nxp.com>
To: Anoob Joseph <anoobj@marvell.com>,
Lukas Bartosik <lbartosik@marvell.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
"radu.nicolau@intel.com" <radu.nicolau@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Lukas Bartosik <lbartosik@marvell.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] examples/ipsec-secgw: update default configuration
Date: Mon, 18 Nov 2019 07:54:01 +0000 [thread overview]
Message-ID: <VE1PR04MB66394E8811D032BC0BA096A4E64D0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <MN2PR18MB28778B70DA841D86C59439E6DF7A0@MN2PR18MB2877.namprd18.prod.outlook.com>
>
> @Akhil, do we need this submitted to dpdk-stable?
>
Yes this is a candidate for stable.
> Acked-by: Anoob Joseph <anoobj@marvell.com>
>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Fixed title and tagged for stable.
Applied to dpdk-next-crypto
Thanks.
parent reply other threads:[~2019-11-18 7:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <MN2PR18MB28778B70DA841D86C59439E6DF7A0@MN2PR18MB2877.namprd18.prod.outlook.com>]
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=VE1PR04MB66394E8811D032BC0BA096A4E64D0@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=lbartosik@marvell.com \
--cc=radu.nicolau@intel.com \
--cc=stable@dpdk.org \
/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).