From: "Liu, Yong" <yong.liu@intel.com>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] tests l2fwd_crypto: add md5 hmac algorithm check
Date: Sun, 18 Sep 2016 14:59:32 +0800 [thread overview]
Message-ID: <57DE3B54.2020007@intel.com> (raw)
In-Reply-To: <9DEEADBC57E43F4DA73B571777FECECA3A58EDBA@shsmsx102.ccr.corp.intel.com>
Thanks, applied into master branch.
On 09/18/2016 02:00 PM, Chen, Zhaoyan wrote:
>> -----Original Message-----
>> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Marvin Liu
>> Sent: Sunday, September 18, 2016 11:22 AM
>> To: dts@dpdk.org
>> Cc: Liu, Yong <yong.liu@intel.com>
>> Subject: [dts] [PATCH] tests l2fwd_crypto: add md5 hmac algorithm check
>>
>> Support md5 hmac algorithm output hash value check.
>> Reduce dut port requirement to only one port.
>> When md5 hmac value is None, calculate it by hmac library.
>>
>> Signed-off-by: Marvin Liu <yong.liu@intel.com>
> Acked-by: Zhaoyan Chen <zhaoyan.chen@intel.com>
prev parent reply other threads:[~2016-09-18 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 3:22 Marvin Liu
2016-09-18 6:00 ` Chen, Zhaoyan
2016-09-18 6:59 ` Liu, Yong [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=57DE3B54.2020007@intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=zhaoyan.chen@intel.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).