From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Jain, Deepak K" <deepak.k.jain@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Griffin, John" <john.griffin@intel.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/qat: fix capabilities for D15xx device
Date: Mon, 10 Apr 2017 13:50:45 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89747806C93@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <A09C9DDE180C7E429EC68E2BFB95C90339594DE0@IRSMSX107.ger.corp.intel.com>
> -----Original Message-----
> From: Jain, Deepak K
> Sent: Monday, April 10, 2017 2:41 PM
> To: Kusztal, ArkadiuszX; dev@dpdk.org
> Cc: Trahe, Fiona; De Lara Guarch, Pablo; Griffin, John
> Subject: RE: [PATCH] crypto/qat: fix capabilities for D15xx device
>
>
> > -----Original Message-----
> > From: Kusztal, ArkadiuszX
> > Sent: Monday, April 10, 2017 2:20 PM
> > To: dev@dpdk.org
> > Cc: Trahe, Fiona <fiona.trahe@intel.com>; De Lara Guarch, Pablo
> > <pablo.de.lara.guarch@intel.com>; Griffin, John <john.griffin@intel.com>;
> > Jain, Deepak K <deepak.k.jain@intel.com>; Kusztal, ArkadiuszX
> > <arkadiuszx.kusztal@intel.com>
> > Subject: [PATCH] crypto/qat: fix capabilities for D15xx device
> >
> > This commit fixes capabilities for Intel(R) QuickAssist Technology D15xx
> > device
> >
> > Fixes: 259310f3a984 ("crypto/qat: support device D15xx")
> >
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> > ---
> > drivers/crypto/qat/rte_qat_cryptodev.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/crypto/qat/rte_qat_cryptodev.c
> default:
> > --
> > 2.7.4
> Acked-by: Deepak Kumar Jain <depak.k.jain@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
next prev parent reply other threads:[~2017-04-10 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 13:20 Arek Kusztal
2017-04-10 13:41 ` Jain, Deepak K
2017-04-10 13:50 ` De Lara Guarch, Pablo [this message]
2017-04-10 13:50 ` Trahe, Fiona
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=E115CCD9D858EF4F90C690B0DCB4D89747806C93@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@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).