linux-kernel - constants vs #define for PCI_DEVICE_/PCI_VENDOR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <CFCBEB88-B9C0-43DA-B69D-1DDB59926946@kernel.crashing.org>
Date:	Fri, 13 Oct 2006 11:13:01 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	"linux-kernel@...r.kernel.org mailing list" 
	<linux-kernel@...r.kernel.org>
Cc:	Greg KH <gregkh@...e.de>
Subject: constants vs #define for PCI_DEVICE_/PCI_VENDOR_

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 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/