From: Jeff Garzik <jeff@garzik.org>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>,
Jim Paradis <jparadis@redhat.com>, Andi Kleen <ak@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
jdmason@kudzu.us
Subject: Re: [PATCH] x86[-64] PCI domain support
Date: Sat, 30 Sep 2006 07:12:27 -0400 [thread overview]
Message-ID: <451E511B.3090704@garzik.org> (raw)
In-Reply-To: <20060930104248.GR22787@rhun.haifa.ibm.com>
Muli Ben-Yehuda wrote:
> So pci_domain_nr and pci_proc_domain are only available if
> CONFIG_PCI_DOMAINS is defined. I followed suit and make pci_iommu only
> available if CONFIG_CALGARY_IOMMU is defined, but perhaps it would be
> better to make it unconditional, since ->sysdata will always be
> available anyway. Was there a specific reason why pci_domain_nr is
> only available if CONFIG_PCI_DOMAINS?
Generic stubs already exist in include/linux/pci.h.
Jeff
next prev parent reply other threads:[~2006-09-30 11:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 19:15 [PATCH] x86[-64] PCI domain support Jeff Garzik
2006-09-26 20:23 ` Greg KH
2006-09-26 20:27 ` Andi Kleen
2006-09-26 20:44 ` Jeff Garzik
2006-09-27 4:40 ` Greg KH
2006-09-27 7:28 ` Rolf Eike Beer
2006-09-28 9:33 ` Muli Ben-Yehuda
2006-09-28 9:45 ` Jeff Garzik
2006-09-28 22:45 ` Muli Ben-Yehuda
2006-09-28 23:03 ` Jeff Garzik
2006-09-28 23:31 ` Muli Ben-Yehuda
2006-09-30 9:34 ` Muli Ben-Yehuda
2006-09-30 10:03 ` Jeff Garzik
2006-09-30 10:42 ` Muli Ben-Yehuda
2006-09-30 11:12 ` Jeff Garzik [this message]
2006-09-30 11:41 ` Jeff Garzik
2006-09-30 17:51 ` [PATCH] x86-64: Calgary IOMMU: update to work with PCI domains Muli Ben-Yehuda
2006-10-01 3:41 ` Jeff Garzik
2006-09-29 13:43 ` [PATCH] x86[-64] PCI domain support Jon Mason
2006-09-29 17:11 ` Muli Ben-Yehuda
2006-09-29 18:24 ` Jon Mason
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=451E511B.3090704@garzik.org \
--to=jeff@garzik.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jdmason@kudzu.us \
--cc=jparadis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.