From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rasesh Mody <Rasesh.Mody@cavium.com>
Cc: dev@dpdk.org, stable@dpdk.org, Dept-EngDPDKDev@cavium.com
Subject: Re: [dpdk-stable] [PATCH v2 1/8] net/qede: fix to get vendor/device id info
Date: Fri, 23 Dec 2016 15:26:24 +0000 [thread overview]
Message-ID: <6173953e-3c29-e9c6-5b37-ee14cb7efe6a@intel.com> (raw)
In-Reply-To: <1482454204-21707-1-git-send-email-Rasesh.Mody@cavium.com>
On 12/23/2016 12:49 AM, Rasesh Mody wrote:
> The vendor_id and device_id are used to determine device type. If you
> don't have them, then check for determining device type fails and is
> always set to default device type.
>
> Fixes: ec94dbc57362 ("qede: add base driver")
>
> Signed-off-by: Rasesh Mody <Rasesh.Mody@cavium.com>
Series applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2016-12-23 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eba57a02-fccd-d0e7-f271-421981e11c7d@intel.com>
2016-12-23 0:49 ` Rasesh Mody
2016-12-23 15:26 ` Ferruh Yigit [this message]
2016-12-23 0:49 ` [dpdk-stable] [PATCH v2 2/8] net/qede/base: fix sriov printouts Rasesh Mody
2016-12-23 0:49 ` [dpdk-stable] [PATCH v2 3/8] net/qede/base: fix multiple acquisition requests by VF Rasesh Mody
2016-12-23 0:50 ` [dpdk-stable] [PATCH v2 4/8] net/qede/base: fix error return code in resc alloc Rasesh Mody
2016-12-23 0:50 ` [dpdk-stable] [PATCH v2 5/8] net/qede/base: fix mutex in freeing context manager Rasesh Mody
2016-12-23 0:50 ` [dpdk-stable] [PATCH v2 6/8] net/qede/base: fix Rx queue access by malicious VFs Rasesh Mody
2016-12-23 0:50 ` [dpdk-stable] [PATCH v2 7/8] net/qede/base: fix to handle acquire request from VF Rasesh Mody
2016-12-23 0:50 ` [dpdk-stable] [PATCH v2 8/8] net/qede/base: fix VF over legacy PF Rasesh Mody
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=6173953e-3c29-e9c6-5b37-ee14cb7efe6a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=Rasesh.Mody@cavium.com \
--cc=dev@dpdk.org \
--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).