From: Greg KH <greg@kroah.com>
To: linas@austin.ibm.com
Cc: linuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6 PCI Hotplug null pointer deref
Date: Fri, 2 Jul 2004 13:56:30 -0700 [thread overview]
Message-ID: <20040702205630.GC29580@kroah.com> (raw)
In-Reply-To: <20040701181605.M21634@forte.austin.ibm.com>
On Thu, Jul 01, 2004 at 06:16:05PM -0500, linas@austin.ibm.com wrote:
>
> Greg,
>
> Please review the attached patch and, if acceptable, apply to the
> akpm/otrvalds/bkbits kernel tree.
>
> This patch fixes a null-pointer dereference when hot-plug operations
> are performed on a machine that has virtual-io devices in it.
> Virtual i/o devices to not have pci bridges associated with them.
> It also corrects an ordering problem during hotplug remove.
>
> This patch was previously reviewed/tested by Linda Xie, the current
> rpaphp maintainer.
>
> --linas
>
> Signed-off-by: Linas Vepstas <linas@linas.org>
Applied, thanks.
greg k-h
prev parent reply other threads:[~2004-07-02 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 23:16 [PATCH] 2.6 PCI Hotplug null pointer deref linas
2004-07-02 20:56 ` 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=20040702205630.GC29580@kroah.com \
--to=greg@kroah.com \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
/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