From: Greg KH <greg@kroah.com>
To: linas@austin.ibm.com
Cc: Linda Xie <lxiep@us.ibm.com>,
linuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org,
pcihpd-discuss@lists.sourceforge.net
Subject: Re: [PATCH] 2.6 PCI Hotplug: receive PPC64 EEH events
Date: Wed, 7 Jul 2004 23:09:33 -0700 [thread overview]
Message-ID: <20040708060933.GE548@kroah.com> (raw)
In-Reply-To: <20040707190642.J21634@forte.austin.ibm.com>
On Wed, Jul 07, 2004 at 07:06:42PM -0500, linas@austin.ibm.com wrote:
> On Wed, Jul 07, 2004 at 07:49:06PM -0500, Linda Xie wrote:
> > linas@austin.ibm.com wrote:
> >
> > > }
> > > sprintf(child_bus->name, "PCI Bus #%02x", child_bus->number);
> > > /* do pci_scan_child_bus */
> > >- pci_scan_child_bus(child_bus);
> > >+ // pci_scan_child_bus(child_bus);
> > >
> > Why remove pci_scan_child_bus call?
>
> Because it won't compile otherwise.
> (Actually, I didn't mean to leave that in the patch,
> it was a work-around to get my tree to compile).
>
> pci_scan_child_bus() is currently defined only as a static fuction
> in drivers/pci/probe.c and thus cannot be called outside of that
> file. Maybe there's a patch to drivers/pci/probe.c that hasn't
> been applied yet?
It's in the latest -bk tree, right?
greg k-h
next prev parent reply other threads:[~2004-07-08 6:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 20:59 [PATCH] 2.6 PCI Hotplug: receive PPC64 EEH events linas
2004-07-07 21:16 ` [Pcihpd-discuss] " Greg KH
2004-07-07 21:47 ` linas
2004-07-08 5:26 ` Greg KH
2004-07-08 15:04 ` linas
2004-07-08 15:12 ` Greg KH
2004-07-08 0:49 ` Linda Xie
2004-07-08 0:06 ` linas
2004-07-08 6:09 ` Greg KH [this message]
2004-07-08 15:24 ` linas
2004-07-08 15:28 ` Greg KH
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=20040708060933.GE548@kroah.com \
--to=greg@kroah.com \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=lxiep@us.ibm.com \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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