From: Simon Horman <horms@verge.net.au>
To: linux-s390@vger.kernel.org, kexec@vger.kernel.org
Subject: Re: [patch 0/2] s390: Patch series for s390 kdump support
Date: Mon, 05 Sep 2011 22:40:06 +0000 [thread overview]
Message-ID: <20110905224006.GC29637@verge.net.au> (raw)
In-Reply-To: <1315216114.15703.5.camel@br98xy6r>
On Mon, Sep 05, 2011 at 11:48:34AM +0200, Michael Holzheu wrote:
> Hello Simon,
>
> On Sat, 2011-08-20 at 18:21 +0900, Simon Horman wrote:
> > On Fri, Aug 19, 2011 at 03:09:49PM +0200, Michael Holzheu wrote:
> > > Hello Simon,
> > >
> > > The following two patches add s390 kdump support (64 bit only) to the
> > > kexec-tools:
> > > [0] Add s390 kdump support
> > > [1] Allow to call verify_sha256_digest() from kernel
> >
> > Thanks, applied.
>
> I checked out kexec-tools git head. Everything worked as expected.
Great. If you have any further patches to kexec-tools please let me know.
next parent reply other threads:[~2011-09-05 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1315216114.15703.5.camel@br98xy6r>
2011-09-05 22:40 ` Simon Horman [this message]
[not found] <20110819130949.289522258@linux.vnet.ibm.com>
2011-08-20 9:21 ` [patch 0/2] s390: Patch series for s390 kdump support Simon Horman
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=20110905224006.GC29637@verge.net.au \
--to=horms@verge.net.au \
--cc=kexec@vger.kernel.org \
--cc=linux-s390@vger.kernel.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