From: Greg KH <greg@kroah.com>
To: Linda Xie <lxiep@us.ibm.com>
Cc: Hotplug List <pcihpd-discuss@lists.sourceforge.net>,
John Rose <johnrose@austin.ibm.com>,
Mike Wortman <wortman@us.ibm.com>,
External List <linuxppc64-dev@lists.linuxppc.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATH] rpaphp_add_slot.patch
Date: Wed, 14 Jul 2004 15:53:09 -0700 [thread overview]
Message-ID: <20040714225309.GD3398@kroah.com> (raw)
In-Reply-To: <40E5E5A1.4080003@us.ibm.com>
On Fri, Jul 02, 2004 at 05:45:53PM -0500, Linda Xie wrote:
> Hi Greg,
>
> I found a bug in rpaphp code during DLPAR I/O testing. When DLPAR ADD
> a non-empty I/O slot to a partition, an adapter in the slot didn't
> get configured. The attached patch fixes that. Please review and apply
> if there are no objections.
>
> Signed-off-by: Linda Xie <lxie@us.ibm.com>
Applied, thanks.
greg k-h
prev parent reply other threads:[~2004-07-14 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 22:45 [PATH] rpaphp_add_slot.patch Linda Xie
2004-07-14 22:53 ` Greg KH [this message]
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=20040714225309.GD3398@kroah.com \
--to=greg@kroah.com \
--cc=johnrose@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 \
--cc=wortman@us.ibm.com \
/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