public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
To: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Cc: Kenji Kaneshige
	<kaneshige.kenji-+CUm20s59erQFUHtdCDX3A@public.gmane.org>,
	Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
	Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Luck, Tony" <tony.luck-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	pcihpd-discuss-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC/PATCH 3/3] ACPI based I/O APIC hot-plug
Date: Fri, 22 Apr 2005 08:15:17 -0700	[thread overview]
Message-ID: <20050422151517.GA29039@kroah.com> (raw)
In-Reply-To: <1114181881.4902.4.camel@eeyore>

On Fri, Apr 22, 2005 at 08:58:01AM -0600, Bjorn Helgaas wrote:
> On Fri, 2005-04-22 at 15:38 +0900, Kenji Kaneshige wrote:
> > Bjorn Helgaas wrote:
> > > 
> > >>+		if ((dev->class >> 8) != PCI_CLASS_SYSTEM_PIC)
> > >>+			continue;
> > >>+		if ((dev->class & 0xff) == 0x10 || (dev->class & 0xff) == 0x20)
> > > 
> > > 
> > > What are 0x10 and 0x20?  Looks like they should be #defines in
> > > include/linux/pci_ids.h.
> > 
> > 0x10 and 0x20 are programing interfaces for I/O APIC and I/O xAPIC
> > respectively. #define for these values looks good. But I don't know
> > if I can put new #defines into pci_ids.h and how to name them because
> > I could not find the header file (including pci_ids.h) that #defines
> > the values for programming interfaces. So I want to add the comments
> > to explain these values (0x10, 0x20) instead of adding new #defines into
> > pci_ids.h for now.
> 
> I think your patch should just add the values to pci_ids.h.  If
> somebody doesn't like that, he or she will complain and you can fall
> back to just using 0x10 and 0x20.  But I suspect it will be fine.

Yes, I have no problem with that.

thanks,

greg k-h


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-04-22 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 13:39 [RFC/PATCH 3/3] ACPI based I/O APIC hot-plug Kenji Kaneshige
2005-04-21 17:22 ` [ACPI] " Bjorn Helgaas
2005-04-22  6:38   ` Kenji Kaneshige
2005-04-22 14:58     ` Bjorn Helgaas
2005-04-22 15:15       ` Greg KH [this message]
2005-04-25  9:16       ` Kenji Kaneshige

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=20050422151517.GA29039@kroah.com \
    --to=greg-u8xffu+wg4eavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=akpm-3NddpPZAyC0@public.gmane.org \
    --cc=bjorn.helgaas-VXdhtT5mjnY@public.gmane.org \
    --cc=kaneshige.kenji-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pcihpd-discuss-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=tony.luck-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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