From: "Cel, TomaszX" <tomaszx.cel@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Jozwiak, TomaszX" <tomaszx.jozwiak@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] drivers/qat: fix failure to create PMD
Date: Thu, 11 Oct 2018 17:27:49 +0000 [thread overview]
Message-ID: <F41EA7C757B0A74DB2ACA0C2C77F1994923442@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <1539278045-28391-1-git-send-email-fiona.trahe@intel.com>
> -----Original Message-----
> From: Trahe, Fiona
> Sent: Thursday, October 11, 2018 7:14 PM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; stable@dpdk.org; Jozwiak, TomaszX
> <tomaszx.jozwiak@intel.com>; Cel, TomaszX <tomaszx.cel@intel.com>;
> Trahe, Fiona <fiona.trahe@intel.com>
> Subject: [PATCH v3] drivers/qat: fix failure to create PMD
>
> If QAT crypto pmd failed to be created due to reaching MAX cryptodevs it
> prevented QAT comp PMD being created. And vice versa.
> Change to warning in these cases and allow the other PMD to be created.
>
> Fixes: c0c90bc4cade ("compress/qat: add create and destroy functions")
> Cc: stable@dpdk.org
>
> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> ---
> v3 changes:
> - moved checks up a layer to the probe fn as more appropriate place.
>
> v2 changes:
> - clarified documentation
>
> drivers/common/qat/qat_device.c | 33 ++++++++++++++++++++++---------
> --
> 1 file changed, 22 insertions(+), 11 deletions(-)
Acked-by: Tomasz Cel <tomaszx.cel@intel.com>
next prev parent reply other threads:[~2018-10-11 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 15:36 [dpdk-dev] [PATCH] " Fiona Trahe
2018-10-01 21:11 ` [dpdk-dev] [PATCH v2] " Fiona Trahe
2018-10-11 17:14 ` [dpdk-dev] [PATCH v3] " Fiona Trahe
2018-10-11 17:27 ` Cel, TomaszX [this message]
2018-10-16 14:37 ` Akhil Goyal
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=F41EA7C757B0A74DB2ACA0C2C77F1994923442@HASMSX110.ger.corp.intel.com \
--to=tomaszx.cel@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=stable@dpdk.org \
--cc=tomaszx.jozwiak@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).