From: Luca Tettamanti <kronos.it@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pci quirks: Sort out the VIA mess once and for all ?(hopefully)
Date: Wed, 8 Nov 2006 20:57:33 +0100 [thread overview]
Message-ID: <20061108195732.GA11067@dreamland.darkstar.lan> (raw)
In-Reply-To: <1163003156.23956.40.camel@localhost.localdomain>
Alan Cox <alan@lxorguk.ukuu.org.uk> ha scritto:
> diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.19-rc4-mm1/include/linux/pci.h linux-2.6.19-rc4-mm1/include/linux/pci.h
> --- linux.vanilla-2.6.19-rc4-mm1/include/linux/pci.h 2006-10-31 21:11:50.000000000 +0000
> +++ linux-2.6.19-rc4-mm1/include/linux/pci.h 2006-11-07 10:07:06.000000000 +0000
> @@ -389,6 +390,21 @@
> .vendor = PCI_ANY_ID, .device = PCI_ANY_ID, \
> .subvendor = PCI_ANY_ID, .subdevice = PCI_ANY_ID
>
> +/**
> + * PCI_VDEVICE - macro used to describe a specific pci device in short form
> + * @vend: the vendor name
> + * @dev: the 16 bit PCI Device ID
> + *
> + * This macro is used to create a struct pci_device_id that matches a
> + * specific PCI device. The vendor, device, subvendor, and subdevice
> + * fields will be set to PCI_ANY_ID. The macro allows the next field
Hello Alan,
the comment doesn't match the macro: vendor and device are passed by the
caller, they're not PCI_ANY_ID.
> + * to follow as the device private data.
> + */
> +
> +#define PCI_VDEVICE(vendor, device) \
> + PCI_VENDOR_ID_##vendor, (device), \
> + PCI_ANY_ID, PCI_ANY_ID, 0, 0
> +
> /* these external functions are only available when PCI support is enabled */
> #ifdef CONFIG_PCI
Luca
--
Recursion n.:
See Recursion.
next prev parent reply other threads:[~2006-11-08 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 16:25 [PATCH] pci quirks: Sort out the VIA mess once and for all (hopefully) Alan Cox
2006-11-08 17:58 ` Jeff Garzik
2006-11-08 19:57 ` Luca Tettamanti [this message]
2006-11-08 20:04 ` Daniel Drake
2006-11-08 20:39 ` Alan Cox
2006-11-09 1:18 ` Sergio Monteiro Basto
2007-04-14 13:22 ` Sergio Monteiro Basto
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=20061108195732.GA11067@dreamland.darkstar.lan \
--to=kronos.it@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox