From: Daniel Kiper <daniel.kiper@oracle.com>
To: Simon Horman <horms@verge.net.au>
Cc: andrew.cooper3@citrix.com,
Eric DeVolder <eric.devolder@oracle.com>,
kexec@lists.infradead.org, konrad.wilk@oracle.com
Subject: Re: [PATCH v5 00/11] kexec: Add option to get crash kernel region size
Date: Thu, 2 Mar 2017 11:10:37 +0100 [thread overview]
Message-ID: <20170302101037.GK28105@olila.local.net-space.pl> (raw)
In-Reply-To: <20170302095151.GA13394@verge.net.au>
On Thu, Mar 02, 2017 at 10:51:51AM +0100, Simon Horman wrote:
> On Fri, Feb 17, 2017 at 04:47:14PM -0600, Eric DeVolder wrote:
> > This is the fifth version of a patch series originally posted by
> > Daniel Kiper on December 5.
>
> Thanks, applied.
Thanks a lot!
Daniel
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2017-03-02 10:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 22:47 [PATCH v5 00/11] kexec: Add option to get crash kernel region size Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 01/11] crashdump/arm: Add get_crash_kernel_load_range() function Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 02/11] crashdump/arm64: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 03/11] crashdump/cris: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 04/11] crashdump/ia64: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 05/11] crashdump/m68k: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 06/11] crashdump/mips: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 07/11] crashdump/ppc: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 08/11] crashdump/ppc64: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 09/11] crashdump/s390: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 10/11] crashdump/sh: " Eric DeVolder
2017-02-17 22:47 ` [PATCH v5 11/11] kexec: Add option to get crash kernel region size Eric DeVolder
2017-03-02 9:51 ` [PATCH v5 00/11] " Simon Horman
2017-03-02 10:10 ` Daniel Kiper [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=20170302101037.GK28105@olila.local.net-space.pl \
--to=daniel.kiper@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=eric.devolder@oracle.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.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