From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI fixes for 2.6.0-test3
Date: Thu, 21 Aug 2003 10:31:09 -0700 [thread overview]
Message-ID: <10614870691817@kroah.com> (raw)
In-Reply-To: <10614870682543@kroah.com>
ChangeSet 1.1123.21.3, 2003/08/18 15:22:01-07:00, greg@kroah.com
[PATCH] PCI: add PCI_DEVICE_CLASS() macro to match PCI_DEVICE() macro.
include/linux/pci.h | 14 ++++++++++++++
1 files changed, 14 insertions(+)
diff -Nru a/include/linux/pci.h b/include/linux/pci.h
--- a/include/linux/pci.h Thu Aug 21 10:22:30 2003
+++ b/include/linux/pci.h Thu Aug 21 10:22:30 2003
@@ -537,6 +537,20 @@
.vendor = (vend), .device = (dev), \
.subvendor = PCI_ANY_ID, .subdevice = PCI_ANY_ID
+/**
+ * PCI_DEVICE_CLASS - macro used to describe a specific pci device class
+ * @dev_class: the class, subclass, prog-if triple for this device
+ * @dev_class_mask: the class mask for this device
+ *
+ * This macro is used to create a struct pci_device_id that matches a
+ * specific PCI class. The vendor, device, subvendor, and subdevice
+ * fields will be set to PCI_ANY_ID.
+ */
+#define PCI_DEVICE_CLASS(dev_class,dev_class_mask) \
+ .class = (dev_class), .class_mask = (dev_class_mask), \
+ .vendor = PCI_ANY_ID, .device = PCI_ANY_ID, \
+ .subvendor = PCI_ANY_ID, .subdevice = PCI_ANY_ID
+
/* these external functions are only available when PCI support is enabled */
#ifdef CONFIG_PCI
next prev parent reply other threads:[~2003-08-21 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 17:29 [BK PATCH] PCI fixes for 2.6.0-test3 Greg KH
2003-08-21 17:31 ` [PATCH] " Greg KH
2003-08-21 17:31 ` Greg KH
2003-08-21 17:31 ` Greg KH [this message]
2003-08-21 17:31 ` Greg KH
2003-08-21 17:31 ` Greg KH
2003-08-21 17:31 ` Greg KH
2003-08-21 17:31 ` Greg KH
2003-08-21 17:31 ` Greg KH
2003-08-21 17:31 ` Greg KH
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=10614870691817@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.