public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: linas@austin.ibm.com
To: Greg KH <greg@kroah.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: Thu, 8 Jul 2004 10:04:33 -0500	[thread overview]
Message-ID: <20040708100433.K21634@forte.austin.ibm.com> (raw)
In-Reply-To: <20040708052603.GA548@kroah.com>; from greg@kroah.com on Wed, Jul 07, 2004 at 10:26:04PM -0700

On Wed, Jul 07, 2004 at 10:26:04PM -0700, Greg KH wrote:
> On Wed, Jul 07, 2004 at 04:47:39PM -0500, linas@austin.ibm.com wrote:
> 
> > ===== drivers/pci/hotplug/rpaphp.h 1.9 vs edited =====
> > +extern void init_eeh_handler (void);
> > +extern void exit_eeh_handler (void);
> 
> This belongs in the eeh header file, not the rpaphp.h file.

But these are implemented in rpaphp_pci.c and are called 
in rpaphp_core.c.  Perchance a different function name, such as
init_rpaphp_eeh_handler() be better?

> > +	// pci_scan_child_bus(child_bus);
> 
> And the reason you are commenting out this function is...

Due to a mistake.

--linas

  reply	other threads:[~2004-07-08 15:05 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 [this message]
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=20040708100433.K21634@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=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