From: Greg KH <greg@kroah.com>
To: linas@austin.ibm.com
Cc: linuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org,
pcihpd-discuss@lists.sourceforge.net
Subject: Re: [Pcihpd-discuss] [PATCH] 2.6 PCI Hotplug: receive PPC64 EEH events
Date: Wed, 7 Jul 2004 22:26:04 -0700 [thread overview]
Message-ID: <20040708052603.GA548@kroah.com> (raw)
In-Reply-To: <20040707164739.I21634@forte.austin.ibm.com>
On Wed, Jul 07, 2004 at 04:47:39PM -0500, linas@austin.ibm.com wrote:
> ===== drivers/pci/hotplug/rpaphp.h 1.9 vs edited =====
> --- 1.9/drivers/pci/hotplug/rpaphp.h Fri Jul 2 11:14:11 2004
> +++ edited/drivers/pci/hotplug/rpaphp.h Wed Jul 7 15:44:35 2004
> @@ -124,7 +124,8 @@
> extern int register_pci_slot(struct slot *slot);
> extern int rpaphp_unconfig_pci_adapter(struct slot *slot);
> extern int rpaphp_get_pci_adapter_status(struct slot *slot, int is_init, u8 * value);
> -extern struct hotplug_slot *rpaphp_find_hotplug_slot(struct pci_dev *dev);
> +extern void init_eeh_handler (void);
> +extern void exit_eeh_handler (void);
This belongs in the eeh header file, not the rpaphp.h file.
> @@ -227,7 +229,7 @@
> }
> 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);
And the reason you are commenting out this function is...
thanks,
greg k-h
next prev parent reply other threads:[~2004-07-08 5:27 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 [this message]
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
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=20040708052603.GA548@kroah.com \
--to=greg@kroah.com \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--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