From: David Marchand <david.marchand@redhat.com>
To: "Singh, Aman Deep" <aman.deep.singh@intel.com>
Cc: Vemula Venkatesh <venkatesh.vemula@intel.com>,
dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Shaiq Wani <shaiq.wani@intel.com>
Subject: Re: [PATCH v1] net/idpf: add IDPF PCI class ID support
Date: Tue, 23 Sep 2025 08:52:18 +0200 [thread overview]
Message-ID: <CAJFAV8xazigsmtQ1OTcU7DyYFF5Z9oZ83n6zAST_qV6LTihBEQ@mail.gmail.com> (raw)
In-Reply-To: <a1edf69a-33ee-41de-b7d3-24f0894734c6@intel.com>
Hello,
On Mon, 22 Sept 2025 at 18:36, Singh, Aman Deep
<aman.deep.singh@intel.com> wrote:
> On Mon, 22 Sept 2025 at 08:35, Vemula Venkatesh
> <venkatesh.vemula@intel.com> wrote:
>
> diff --git a/drivers/net/intel/idpf/idpf_common_device.h b/drivers/net/intel/idpf/idpf_common_device.h
> index 5f3e4a4fcf..9d1d7dc47c 100644
> --- a/drivers/net/intel/idpf/idpf_common_device.h
> +++ b/drivers/net/intel/idpf/idpf_common_device.h
> @@ -44,6 +44,23 @@
> (sizeof(struct virtchnl2_ptype) + \
> (((p)->proto_id_count ? ((p)->proto_id_count - 1) : 0) * sizeof((p)->proto_id[0])))
>
> +/** Macro used to help building up tables of device IDs with PCI class */
> +#define RTE_PCI_CLASS(cls) \
> + .class_id = (cls), \
> + .vendor_id = RTE_PCI_ANY_ID, \
> + .device_id = RTE_PCI_ANY_ID, \
> + .subsystem_vendor_id = RTE_PCI_ANY_ID, \
> + .subsystem_device_id = RTE_PCI_ANY_ID
>
> Don't define a macro with the RTE_PCI_ namespace in a driver.
>
> Either this is really specific to IDPF, and this should be renamed
> with a prefix reflecting this.
> This macro is a huge wildcard on a pci class, which seems very specific.
>
> Or this makes sense for other drivers and then this macro should be
> moved to the pci bus driver header.
>
> Yes David, it only applies to IDPF. As per PCI document-
>
> https://members.pcisig.com/document/20113 Table: 1.3
I'll trust you, as I don't have access.
>
> Is it OK to rename it: IDPF_PCI_CLASS ?
Ok for me.
Thank you.
--
David Marchand
next prev parent reply other threads:[~2025-09-23 6:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 14:51 Vemula Venkatesh
2025-09-22 8:31 ` Wani, Shaiq
2025-09-22 12:09 ` David Marchand
2025-09-22 16:35 ` Singh, Aman Deep
2025-09-23 6:52 ` David Marchand [this message]
2025-09-24 12:57 ` [PATCH v2] net/intel: " Vemula Venkatesh
2025-09-24 14:34 ` Bruce Richardson
2025-09-25 10:28 ` Vemula, Venkatesh
2025-09-25 17:47 ` [PATCH v3] " Vemula Venkatesh
2025-09-26 15:26 ` Singh, Aman Deep
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=CAJFAV8xazigsmtQ1OTcU7DyYFF5Z9oZ83n6zAST_qV6LTihBEQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aman.deep.singh@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=shaiq.wani@intel.com \
--cc=venkatesh.vemula@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).