From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Matthew Wilcox <matthew@wil.cx>, Alex Chiang <achiang@hp.com>,
jbarnes@virtuousgeek.org, linux-arch@vger.kernel.org,
Kyle McMartin <kyle@mcmartin.ca>, Tony Luck <tony.luck@intel.com>,
Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
David Howells <dhowells@redhat.com>,
Paul Mundt <lethal@linux-sh.org>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Ingo Molnar <mingo@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Avi Kivity <avi@redhat.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>
Subject: Re: [PATCH] PCI: remove pcibios_scan_all_fns()
Date: Wed, 24 Jun 2009 08:41:56 +1000 [thread overview]
Message-ID: <1245796916.10356.40.camel@pasglop> (raw)
In-Reply-To: <4A41562F.1040901@goop.org>
On Tue, 2009-06-23 at 15:24 -0700, Jeremy Fitzhardinge wrote:
> I guess we could fake up OF-like datastructures or something, but I
> don't see what wide application that would have. It might help in this
> case, but its a lot more complex than just calling
> pci_scan_single_device() at the appropriate place.
It would be indeed more complex and probably not something to do
right now to solve that specific problem
> Do you have any other cases in mind where it would be helpful?
Well, it might be for virtual device discovery etc... but don't bother
now. We might talk about it at KS for those interested. It's more
something we see as useful for embedded archs at the moment but in the
long run it might make sense for hypervisors as well.
Cheers,
Ben.
next prev parent reply other threads:[~2009-06-23 22:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 14:08 [PATCH] PCI: remove pcibios_scan_all_fns() Alex Chiang
2009-06-22 14:21 ` Kyle McMartin
2009-06-22 14:26 ` Ralf Baechle
2009-06-22 14:36 ` Matthew Wilcox
2009-06-22 14:34 ` Matthew Wilcox
2009-06-22 14:34 ` Matthew Wilcox
2009-06-22 18:20 ` Jeremy Fitzhardinge
2009-06-22 18:30 ` Matthew Wilcox
2009-06-22 23:40 ` Benjamin Herrenschmidt
2009-06-23 19:08 ` Matthew Wilcox
2009-06-23 20:34 ` Jeremy Fitzhardinge
2009-06-23 20:56 ` Matthew Wilcox
2009-06-23 21:49 ` Benjamin Herrenschmidt
2009-06-23 22:24 ` Jeremy Fitzhardinge
2009-06-23 22:41 ` Benjamin Herrenschmidt [this message]
2009-06-23 22:53 ` Jeremy Fitzhardinge
2009-06-24 0:02 ` Benjamin Herrenschmidt
2009-06-24 10:30 ` Ian Campbell
2009-06-24 10:30 ` Ian Campbell
2009-06-23 21:47 ` Benjamin Herrenschmidt
2009-06-22 23:55 ` Jeremy Fitzhardinge
2009-06-23 0:33 ` Benjamin Herrenschmidt
2009-06-23 1:43 ` Chris Wright
2009-06-23 2:22 ` Benjamin Herrenschmidt
2009-06-23 18:29 ` Avi Kivity
2009-06-22 15:29 ` Russell King - ARM Linux
2009-06-22 16:53 ` Arnd Bergmann
2009-06-23 16:43 ` Paul Mundt
2009-06-29 20:33 ` Jesse Barnes
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=1245796916.10356.40.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=achiang@hp.com \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jbarnes@virtuousgeek.org \
--cc=jdike@addtoit.com \
--cc=jeremy@goop.org \
--cc=kyle@mcmartin.ca \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=matthew@wil.cx \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.org \
--cc=tony.luck@intel.com \
--cc=ysato@users.sourceforge.jp \
/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;
as well as URLs for NNTP newsgroup(s).