From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Jain, Deepak K" <deepak.k.jain@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] tools: add crypto device details
Date: Wed, 21 Sep 2016 18:56:17 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C9FB9A5@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <A09C9DDE180C7E429EC68E2BFB95C9033945EB08@IRSMSX107.ger.corp.intel.com>
> -----Original Message-----
> From: Jain, Deepak K
> Sent: Wednesday, September 21, 2016 3:04 AM
> To: De Lara Guarch, Pablo; dev@dpdk.org
> Subject: RE: [PATCH v4] tools: add crypto device details
>
>
> > -----Original Message-----
> > From: De Lara Guarch, Pablo
> > Sent: Tuesday, September 20, 2016 1:05 AM
> > To: dev@dpdk.org
> > Cc: Jain, Deepak K <deepak.k.jain@intel.com>; Eoin Breen
> > <eoin.breen@intel.com>; De Lara Guarch, Pablo
> > <pablo.de.lara.guarch@intel.com>
> > Subject: [PATCH v4] tools: add crypto device details
> >
> > From: Eoin Breen <eoin.breen@intel.com>
> >
> > Adding the support to bind/unbind crypto devices with dpdk-devbind.py
> > script, as now it is not restricted to network devices anymore.
> >
> > Signed-off-by: Eoin Breen <eoin.breen@intel.com>
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> > ---
> > Changes since v3:
> > * Modified setup.sh script to show crypto details
> > * Added script usage in qat.rst doc
> > * Modified help script, to include crypto references
> >
> > Changes since v2:
> > * Removed network specific parameters from crypto parameters
> >
> > Changes since v1:
> > * Resolved coding issues
> >
> > doc/guides/cryptodevs/qat.rst | 5 +++
> > tools/dpdk-devbind.py | 94
> > ++++++++++++++++++++++++++++++++++++++-----
> > tools/dpdk-setup.sh | 32 +++++++--------
> > 3 files changed, 105 insertions(+), 26 deletions(-)
> > --
> > 2.7.4
> Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2016-09-21 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 10:04 [dpdk-dev] [PATCH] " Eoin Breen
2016-08-25 10:32 ` Mcnamara, John
2016-08-25 13:52 ` [dpdk-dev] [PATCH v2] " Eoin Breen
2016-08-25 20:31 ` Jain, Deepak K
2016-09-13 22:50 ` De Lara Guarch, Pablo
2016-09-15 23:57 ` [dpdk-dev] [PATCH v3] " Pablo de Lara
2016-09-20 0:05 ` [dpdk-dev] [PATCH v4] " Pablo de Lara
2016-09-21 10:04 ` Jain, Deepak K
2016-09-21 18:56 ` 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=E115CCD9D858EF4F90C690B0DCB4D8973C9FB9A5@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@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).