From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Jain, Deepak K" <deepak.k.jain@intel.com>,
"Griffin, John" <john.griffin@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add limitations section to cryptoperf guide
Date: Thu, 9 Feb 2017 23:24:44 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476D7C3C@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <158888A50F43E34AAE179517F56C9745653297@IRSMSX103.ger.corp.intel.com>
> -----Original Message-----
> From: Mrozowicz, SlawomirX
> Sent: Wednesday, February 08, 2017 9:48 AM
> To: Trahe, Fiona; dev@dpdk.org
> Cc: De Lara Guarch, Pablo; Jain, Deepak K; Griffin, John; Doherty, Declan
> Subject: RE: [PATCH] doc: add limitations section to cryptoperf guide
>
>
>
> >-----Original Message-----
> >From: Trahe, Fiona
> >Sent: Tuesday, February 7, 2017 5:33 PM
> >To: dev@dpdk.org
> >Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Mrozowicz,
> >SlawomirX <slawomirx.mrozowicz@intel.com>; Jain, Deepak K
> ><deepak.k.jain@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>; Griffin,
> >John <john.griffin@intel.com>; Doherty, Declan
> <declan.doherty@intel.com>
> >Subject: [PATCH] doc: add limitations section to cryptoperf guide
> >
> >Add limitations to use of the dpdk-test-crypto-perf tool for hardware
> >accelerator measurements
> >
> >Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
...
> Acked-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2017-02-09 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 16:32 Trahe, Fiona
2017-02-08 9:31 ` Mrozowicz, SlawomirX
2017-02-08 9:47 ` Mrozowicz, SlawomirX
2017-02-09 23:24 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D897476D7C3C@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@intel.com \
--cc=slawomirx.mrozowicz@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).