From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] doc: fix crypto scheduler command line examples
Date: Tue, 11 Jul 2017 14:10:19 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBD9F3B@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23ED2549F@IRSMSX104.ger.corp.intel.com>
> -----Original Message-----
> From: Mcnamara, John
> Sent: Friday, July 7, 2017 1:47 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Doherty,
> Declan <declan.doherty@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: RE: [PATCH] doc: fix crypto scheduler command line examples
>
>
>
> > -----Original Message-----
> > From: De Lara Guarch, Pablo
> > Sent: Friday, July 7, 2017 5:37 AM
> > To: Mcnamara, John <john.mcnamara@intel.com>; Doherty, Declan
> > <declan.doherty@intel.com>
> > Cc: dev@dpdk.org; De Lara Guarch, Pablo
> > <pablo.de.lara.guarch@intel.com>; stable@dpdk.org
> > Subject: [PATCH] doc: fix crypto scheduler command line examples
> >
> > Sample command lines for crypto scheduler were not correct, due to:
> > - Typo in "crypto_scheduler" driver name
> > - Multiple virtual devices require having unique names,
> > driver name + a suffix, otherwise, just a single device is
> > created.
> >
> > Fixes: d58a3f312545 ("crypto/scheduler: add documentation")
> > CC: stable@dpdk.org
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied to dpdk-next-crypto.
Pablo
prev parent reply other threads:[~2017-07-11 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 4:36 Pablo de Lara
2017-07-07 12:46 ` Mcnamara, John
2017-07-11 14:10 ` 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=E115CCD9D858EF4F90C690B0DCB4D8976CBD9F3B@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).