public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Grant Grundler <grundler@parisc-linux.org>,
	Jason Gaston <jason.d.gaston@intel.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
	linux-pci@atrey.karlin.mff.cuni.cz, khali@linux-fr.org,
	i2c@lm-sensors.nu
Subject: Re: [PATCH 2.6.23-rc4] irq: irq and pci_ids patch for Intel Tolapai
Date: Sat, 01 Sep 2007 17:30:58 -0400	[thread overview]
Message-ID: <46D9DA12.6050805@garzik.org> (raw)
In-Reply-To: <20070901211939.GA10442@colo.lackof.org>

Grant Grundler wrote:
> On Thu, Aug 30, 2007 at 03:46:56PM -0700, Jason Gaston wrote:
>> This updated patch adds the Intel Tolapai LPC and SMBus Controller DID's.
>>
>> Signed-off-by: ?Jason Gaston <jason.d.gaston@intel.com>
>>
>> --- linux-2.6.23-rc4/arch/i386/pci/irq.c.orig	2007-08-27 18:32:35.000000000 
>> -0700
>> +++ linux-2.6.23-rc4/arch/i386/pci/irq.c	2007-08-28 16:58:31.000000000 -0700
>> @@ -550,6 +550,7 @@
>>  		case PCI_DEVICE_ID_INTEL_ICH9_3:
>>  		case PCI_DEVICE_ID_INTEL_ICH9_4:
>>  		case PCI_DEVICE_ID_INTEL_ICH9_5:
>> +		case PCI_DEVICE_ID_INTEL_Tolapai_0:
> 
> If this is the only place it's used, the prefence is to define the
> constant locally (in the file) and not in pci_ids.h.

Kinda sorta:  if you must define a constant, it should go into 
linux/pci_ids.h.  Otherwise someone will come along later, do the same 
locally in another file, then you have two independent symbols with the 
same meaning.

Ideally, in pci_device_id tables and such, you can just use the hex 
number, since they are all arbitrary and lack meaning anyway.


> Please do submit new PCI device IDs to pciids.sf.net project.

Yep.


>>  #define PCI_DEVICE_ID_INTEL_MCH_PC	0x3599
>>  #define PCI_DEVICE_ID_INTEL_MCH_PC1	0x359a
>>  #define PCI_DEVICE_ID_INTEL_E7525_MCH	0x359e
>> +#define PCI_DEVICE_ID_INTEL_Tolapai_0	0x5031
>> +#define PCI_DEVICE_ID_INTEL_Tolapai_1	0x5032

And change the StudlyCaps to ALLCAPS.

	Jeff




  reply	other threads:[~2007-09-01 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 22:46 [PATCH 2.6.23-rc4] irq: irq and pci_ids patch for Intel Tolapai Jason Gaston
2007-08-31  1:41 ` Matthew Wilcox
2007-09-01 21:19 ` Grant Grundler
2007-09-01 21:30   ` Jeff Garzik [this message]
2007-09-04 17:17     ` Gaston, Jason D

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=46D9DA12.6050805@garzik.org \
    --to=jeff@garzik.org \
    --cc=gregkh@suse.de \
    --cc=grundler@parisc-linux.org \
    --cc=i2c@lm-sensors.nu \
    --cc=jason.d.gaston@intel.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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