From: Jeff Garzik <jeff@garzik.org>
To: Thomas Klein <osstklei@de.ibm.com>
Cc: netdev <netdev@vger.kernel.org>,
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>,
Marcus Eder <meder@de.ibm.com>, Thomas Klein <tklein@de.ibm.com>
Subject: Re: [PATCH] ehea: add kdump support
Date: Wed, 20 Feb 2008 11:50:42 -0500 [thread overview]
Message-ID: <47BC5A62.2030701@garzik.org> (raw)
In-Reply-To: <47B30A49.8080404@de.ibm.com>
Thomas Klein wrote:
> This patch adds kdump support to the ehea driver. As the firmware doesn't free
> resource handles automatically, the driver has to run an as simple as possible
> free resource function in case of a crash shutdown. The function iterates over
> two arrays freeing all resource handles which are stored there. The arrays are
> kept up-to-date during normal runtime. The crash handler fn is triggered by the
> recently introduced PPC crash shutdown reg/unreg functions.
>
>
> Signed-off-by: Thomas Klein <tklein@de.ibm.com>
>
> ---
> drivers/net/ehea/ehea.h | 34 +++++-
> drivers/net/ehea/ehea_main.c | 281 ++++++++++++++++++++++++++++++++++++++----
> 2 files changed, 290 insertions(+), 25 deletions(-)
applied
next prev parent reply other threads:[~2008-02-20 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 15:18 [PATCH] ehea: add kdump support Thomas Klein
2008-02-20 16:50 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-09 13:33 [PATCH] ehea: Add " Thomas Klein
2007-11-10 0:20 ` Michael Neuling
2007-11-26 8:16 ` Michael Ellerman
2007-11-26 10:45 ` Christoph Raisch
2007-11-27 0:35 ` Michael Neuling
2007-11-26 15:41 ` Luke Browning
2007-11-26 18:11 ` Linas Vepstas
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=47BC5A62.2030701@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=meder@de.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=osstklei@de.ibm.com \
--cc=raisch@de.ibm.com \
--cc=themann@de.ibm.com \
--cc=tklein@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).