From: Greg KH <greg@kroah.com>
To: Jake Moilanen <moilanen@austin.ibm.com>, johnrose@austin.ibm.com
Cc: Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>,
torvalds@osdl.org
Subject: Re: [PATCH][2.6] PCI Scan all functions
Date: Tue, 27 Jan 2004 13:12:53 -0800 [thread overview]
Message-ID: <20040127211253.GA27583@kroah.com> (raw)
In-Reply-To: <1075222501.1030.45.camel@magik>
On Tue, Jan 27, 2004 at 10:55:01AM -0600, Jake Moilanen wrote:
> There are some arch, like PPC64, that need to be able to scan all the
> PCI functions. The problem comes in on a logically partitioned system
> where function 0 on a PCI-PCI bridge is assigned to one partition and
> say function 2 is assiged to another partition. On the second
> partition, it would appear that function 0 does not exist, but function
> 2 does. If all the functions are not scanned, everything under function
> 2 would not be detected.
Heh, I think the PPC64 people need to get together and all talk about
this, as I just got a different patch, that solves much the same problem
from John Rose (it's on the linuxppc64 mailing list.)
Can you two get together and not patch the same section of code to do
the same thing in different ways?
thanks,
greg k-h
next prev parent reply other threads:[~2004-01-27 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 16:55 [PATCH][2.6] PCI Scan all functions Jake Moilanen
2004-01-27 21:12 ` Greg KH [this message]
2004-01-27 21:33 ` Andrew Morton
2004-01-27 21:44 ` Greg KH
2004-01-28 20:58 ` Ivan Kokshaysky
2004-01-27 21:57 ` Linus Torvalds
2004-01-27 21:57 ` John Rose
2004-01-28 15:41 ` Martin Mares
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=20040127211253.GA27583@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=johnrose@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moilanen@austin.ibm.com \
--cc=torvalds@osdl.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