From: "Liang, Cunming" <cunming.liang@intel.com>
To: "Yang, Ziye" <ziye.yang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Ziye" <ziye.yang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] PCI: ABI change request for adding new field in rte_pci_id structure
Date: Thu, 18 Feb 2016 02:46:18 +0000 [thread overview]
Message-ID: <D0158A423229094DA7ABF71CF2FA0DA314AFE340@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1455674073-16579-1-git-send-email-ziye.yang@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ziye Yang
> Sent: Wednesday, February 17, 2016 9:55 AM
> To: dev@dpdk.org
> Cc: Yang, Ziye
> Subject: [dpdk-dev] [PATCH v3] PCI: ABI change request for adding new field in
> rte_pci_id structure
>
> From: Ziye <ziye.yang@intel.com>
>
> The purpose of this patch is used to add a new field
> "class" in rte_pci_id structure. The new class field includes
> class_id, subcalss_id, programming interface of a pci device.
> With this field, we can identify pci device by its class info,
> which can be more flexible instead of probing the device by
> vendor_id OR device_id OR subvendor_id OR subdevice_id.
> For example, we can probe all nvme devices by class field, which
> can be quite convenient.
>
> Signed-off-by: Ziye Yang <ziye.yang@intel.com>
It's better to use "doc:" as subject prefix, the others are good to go.
Acked-by: Cunming Liang <cunming.liang@intel.com>
prev parent reply other threads:[~2016-02-18 2:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 2:36 [dpdk-dev] [PATCH] " Ziye Yang
2016-02-16 4:15 ` [dpdk-dev] [PATCH v2] " Ziye Yang
2016-02-16 10:11 ` Bruce Richardson
2016-02-16 10:34 ` Thomas Monjalon
2016-02-17 1:54 ` [dpdk-dev] [PATCH v3] " Ziye Yang
2016-02-17 10:14 ` Bruce Richardson
2016-04-05 15:31 ` Thomas Monjalon
2016-02-18 1:57 ` Zhang, Helin
2016-02-18 2:46 ` Liang, Cunming [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=D0158A423229094DA7ABF71CF2FA0DA314AFE340@SHSMSX101.ccr.corp.intel.com \
--to=cunming.liang@intel.com \
--cc=dev@dpdk.org \
--cc=ziye.yang@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).