DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ziye Yang <ziye.yang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] ci: Add the class_id support in pci probe
Date: Tue, 24 May 2016 11:29:33 +0200	[thread overview]
Message-ID: <3830854.ocOkRYbjrN@xps13> (raw)
In-Reply-To: <1463663877-52722-1-git-send-email-ziye.yang@intel.com>

Hi Ziye,

Please check the title.
It could be "pci: add class id".

Please try to add a changelog below the 3 dashes when making a new revision.

Other comments below:

2016-05-19 21:17, Ziye Yang:
> --- a/lib/librte_eal/common/include/rte_pci.h
> +++ b/lib/librte_eal/common/include/rte_pci.h
> @@ -125,6 +125,7 @@ struct rte_pci_resource {
>   * table of these IDs for each device that it supports.
>   */
>  struct rte_pci_id {
> +	uint32_t class_id;            /**< Class ID (class, subclass, pi) or RTE_CLASS_ANY_ID. */
>  	uint16_t vendor_id;           /**< Vendor ID or PCI_ANY_ID. */
>  	uint16_t device_id;           /**< Device ID or PCI_ANY_ID. */
>  	uint16_t subsystem_vendor_id; /**< Subsystem vendor ID or PCI_ANY_ID. */

You moved class_id at the beginning (which looks good)...

> @@ -177,14 +179,16 @@ struct rte_pci_device {
>  	(vend),                   \
>  	(dev),                    \
>  	PCI_ANY_ID,               \
> -	PCI_ANY_ID
> +	PCI_ANY_ID,               \
> +	RTE_CLASS_ANY_ID
>  #else
>  /** Macro used to help building up tables of device IDs */
>  #define RTE_PCI_DEVICE(vend, dev)          \
>  	.vendor_id = (vend),               \
>  	.device_id = (dev),                \
>  	.subsystem_vendor_id = PCI_ANY_ID, \
> -	.subsystem_device_id = PCI_ANY_ID
> +	.subsystem_device_id = PCI_ANY_ID, \
> +	.class_id = RTE_CLASS_ANY_ID
>  #endif

... but forgot to move these lines.

  reply	other threads:[~2016-05-24  9:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11  6:08 [dpdk-dev] [PATCH] pci: " Ziye Yang
2016-05-11 15:21 ` Stephen Hemminger
2016-05-11 15:34   ` Richardson, Bruce
2016-05-19 10:33 ` Thomas Monjalon
2016-05-19 12:18   ` Yang, Ziye
2016-05-19 12:57     ` Thomas Monjalon
2016-05-19 13:14       ` Yang, Ziye
2016-05-19 12:25 ` [dpdk-dev] [PATCH v2] ci: " Ziye Yang
2016-05-19 13:17   ` [dpdk-dev] [PATCH v3] " Ziye Yang
2016-05-24  9:29     ` Thomas Monjalon [this message]
2016-05-24 12:50     ` [dpdk-dev] [PATCH v4] Pci: Add the class_id support Ziye Yang
2016-06-14 14:52       ` Thomas Monjalon
2016-07-06 11:08         ` Ferruh Yigit
2016-07-07  7:46           ` 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=3830854.ocOkRYbjrN@xps13 \
    --to=thomas.monjalon@6wind.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).