From: Thomas Monjalon <thomas@monjalon.net>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Cc: dev@dpdk.org, "Kovacevic, Marko" <marko.kovacevic@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] examples/fips_validation: fix physical address
Date: Tue, 22 Jan 2019 17:32:52 +0100 [thread overview]
Message-ID: <2271104.AuG9yKJBGo@xps> (raw)
In-Reply-To: <6DC05C7C5F25994B81B3F2F214251F660207F047@IRSMSX104.ger.corp.intel.com>
22/01/2019 16:46, Kovacevic, Marko:
> > This patch fixes the missed digest and aad data physical addresses filling to
> > crypto operations in fips_validation sample application.
> >
> > Fixes: 41d561cbdd24 ("examples/fips_validation: add power on self test")
> >
> > Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
>
> Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
Applied, thanks
prev parent reply other threads:[~2019-01-22 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 9:15 Fan Zhang
2019-01-22 15:46 ` Kovacevic, Marko
2019-01-22 16:32 ` Thomas Monjalon [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=2271104.AuG9yKJBGo@xps \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.com \
--cc=roy.fan.zhang@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).