From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] examples/ipsec-secgw: fix debug in ipsec-secgw app
Date: Tue, 19 Mar 2019 14:06:14 +0000 [thread overview]
Message-ID: <c124ec28-c047-90ca-6f18-842f4bc5b69a@nxp.com> (raw)
In-Reply-To: <6be72316-6c48-d95a-5d55-df0a4208e277@nxp.com>
On 3/19/2019 7:13 PM, Akhil Goyal wrote:
>
> On 3/8/2019 9:05 PM, Ananyev, Konstantin wrote:
>>> -----Original Message-----
>>> From: Iremonger, Bernard
>>> Sent: Thursday, March 7, 2019 10:35 AM
>>> To: dev@dpdk.org; Ananyev, Konstantin <konstantin.ananyev@intel.com>; akhil.goyal@nxp.com
>>> Cc: Iremonger, Bernard <bernard.iremonger@intel.com>; stable@dpdk.org
>>> Subject: [PATCH] examples/ipsec-secgw: fix debug in ipsec-secgw app
>>>
>>> Improve debug code in esp.c, sa.c and ipsec-secgw.c
>>>
>>> Fixes: f159e70b0922 ("examples/ipsec-secgw: support transport mode")
>>> Fixes: ec17993a145a ("examples/ipsec-secgw: support security offload")
>>> Fixes: 0d547ed03717 ("examples/ipsec-secgw: support configuration file")
>>> Fixes: 906257e965b7 ("examples/ipsec-secgw: support IPv6")
>>> Cc: stable@dpdk.org
>>>
>>> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
>>> ---
>> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
>>
>>> 2.7.4
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2019-03-19 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 10:34 [dpdk-stable] " Bernard Iremonger
2019-03-08 15:35 ` Ananyev, Konstantin
2019-03-19 13:43 ` [dpdk-stable] [dpdk-dev] " Akhil Goyal
2019-03-19 14:06 ` Akhil Goyal [this message]
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=c124ec28-c047-90ca-6f18-842f4bc5b69a@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@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).