From: Kumar Gala <galak@kernel.crashing.org>
To: "linux-kernel@vger.kernel.org mailing list"
<linux-kernel@vger.kernel.org>
Cc: Greg KH <gregkh@suse.de>
Subject: constants vs #define for PCI_DEVICE_/PCI_VENDOR_
Date: Fri, 13 Oct 2006 11:13:01 -0500 [thread overview]
Message-ID: <CFCBEB88-B9C0-43DA-B69D-1DDB59926946@kernel.crashing.org> (raw)
I remember some discussion back and forth about the use of constants
in pci_device_id entries versus defining new PCI_DEVICE_foo/
PCI_VENDOR_foo defines. What is the current coding style of choice
if the vendor & device id's dont exit in pci_ids.h?
- kumar
reply other threads:[~2006-10-13 16:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CFCBEB88-B9C0-43DA-B69D-1DDB59926946@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=gregkh@suse.de \
--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
all inboxes | Powered by JetHome®