From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Pattan, Reshma" <reshma.pattan@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] app/test: enhance cryptodev scheduler unit tests
Date: Wed, 9 May 2018 10:33:11 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CD04F7F@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CD04F47@IRSMSX108.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch, Pablo
> Sent: Wednesday, May 9, 2018 11:31 AM
> To: Pattan, Reshma <reshma.pattan@intel.com>; dev@dpdk.org
> Cc: Parthasarathy, JananeeX M <jananeex.m.parthasarathy@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v3] app/test: enhance cryptodev scheduler unit
> tests
>
>
>
> > -----Original Message-----
> > From: Pattan, Reshma
> > Sent: Friday, April 13, 2018 10:00 AM
> > To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
> > dev@dpdk.org
> > Cc: Parthasarathy, JananeeX M <jananeex.m.parthasarathy@intel.com>
> > Subject: [PATCH v3] app/test: enhance cryptodev scheduler unit tests
> >
> > Unit Test Cases for MultiCore mode, Failover mode, Packet Distribution
> > mode are added to improve code coverage
> >
> > Signed-off-by: Jananee Parthasarathy
> > <jananeex.m.parthasarathy@intel.com>
>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2018-05-09 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 13:55 [dpdk-dev] [PATCH] " Reshma Pattan
2018-04-10 12:16 ` [dpdk-dev] [PATCH v2] " Reshma Pattan
2018-04-13 9:00 ` [dpdk-dev] [PATCH v3] " Reshma Pattan
2018-05-09 10:30 ` De Lara Guarch, Pablo
2018-05-09 10:33 ` 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=E115CCD9D858EF4F90C690B0DCB4D8976CD04F7F@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=jananeex.m.parthasarathy@intel.com \
--cc=reshma.pattan@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).