From: Deepak Kumar Jain <deepak.k.jain@intel.com>
To: dev@dpdk.org
Cc: pablo.de.lara.guarch@intel.com, john.griffin@intel.com, "Jain,
Deepak K" <deepak.k.jain@intel.com>
Subject: [dpdk-dev] [PATCH v3] qat: fix for VFs not getting recognized
Date: Tue, 21 Jun 2016 10:03:41 +0100 [thread overview]
Message-ID: <1466499821-205232-1-git-send-email-deepak.k.jain@intel.com> (raw)
In-Reply-To: <1466087775-235077-1-git-send-email-deepak.k.jain@intel.com>
From: "Jain, Deepak K" <deepak.k.jain@intel.com>
Updated the code to use RTE_PCI_DEVICE.
Fixes: 701c8d80c820 ("pci: support class id probing")
Signed-off-by: Jain, Deepak K <deepak.k.jain@intel.com>
---
v3: kept PCI id in the driver file
v2: updated code to use RTE_PCI_DEVICE
drivers/crypto/qat/rte_qat_cryptodev.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/crypto/qat/rte_qat_cryptodev.c b/drivers/crypto/qat/rte_qat_cryptodev.c
index a7912f5..f46ec85 100644
--- a/drivers/crypto/qat/rte_qat_cryptodev.c
+++ b/drivers/crypto/qat/rte_qat_cryptodev.c
@@ -69,10 +69,7 @@ static struct rte_cryptodev_ops crypto_qat_ops = {
static struct rte_pci_id pci_id_qat_map[] = {
{
- .vendor_id = 0x8086,
- .device_id = 0x0443,
- .subsystem_vendor_id = PCI_ANY_ID,
- .subsystem_device_id = PCI_ANY_ID
+ RTE_PCI_DEVICE(0x8086, 0x0443),
},
{.device_id = 0},
};
--
2.5.5
next prev parent reply other threads:[~2016-06-21 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1466087775-235077-1-git-send-email-deepak.k.jain@intel.com>
2016-06-20 16:10 ` [dpdk-dev] [PATCH v2] " Jain, Deepak K
2016-06-20 17:08 ` Thomas Monjalon
2016-06-21 9:03 ` Deepak Kumar Jain [this message]
2016-06-21 13:37 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
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=1466499821-205232-1-git-send-email-deepak.k.jain@intel.com \
--to=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=john.griffin@intel.com \
--cc=pablo.de.lara.guarch@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).