All of lore.kernel.org
 help / color / mirror / Atom feed
From: linas@austin.ibm.com
To: Linda Xie <lxiep@us.ibm.com>
Cc: greg@kroah.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 19:06:42 -0500	[thread overview]
Message-ID: <20040707190642.J21634@forte.austin.ibm.com> (raw)
In-Reply-To: <40EC9A02.1000507@us.ibm.com>; from lxiep@us.ibm.com on Wed, Jul 07, 2004 at 07:49:06PM -0500

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?

--linas

  reply	other threads:[~2004-07-08  5:59 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 [this message]
2004-07-08  6:09     ` Greg KH
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=20040707190642.J21634@forte.austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=greg@kroah.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 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.