From: Jeff Garzik <jeff@garzik.org>
To: Thomas Klein <osstklei@de.ibm.com>
Cc: Christoph Raisch <raisch@de.ibm.com>,
Jan-Bernd Themann <themann@de.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ppc <linuxppc-dev@ozlabs.org>,
netdev <netdev@vger.kernel.org>,
Stefan Roscher <stefan.roscher@de.ibm.com>,
Hannes Hering <hering2@de.ibm.com>
Subject: Re: [PATCH] ehea: Fix DLPAR memory add support
Date: Sat, 12 Apr 2008 04:49:53 -0400 [thread overview]
Message-ID: <480077B1.3010804@garzik.org> (raw)
In-Reply-To: <200804041504.54130.osstklei@de.ibm.com>
Thomas Klein wrote:
> This patch fixes two weaknesses in send/receive packet handling which may
> lead to kernel panics during DLPAR memory add operations.
>
> Signed-off-by: Thomas Klein <tklein@de.ibm.com>
applied
prev parent reply other threads:[~2008-04-12 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 13:04 [PATCH] ehea: Fix DLPAR memory add support Thomas Klein
2008-04-12 8:49 ` Jeff Garzik [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=480077B1.3010804@garzik.org \
--to=jeff@garzik.org \
--cc=hering2@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=osstklei@de.ibm.com \
--cc=raisch@de.ibm.com \
--cc=stefan.roscher@de.ibm.com \
--cc=themann@de.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;
as well as URLs for NNTP newsgroup(s).