From: Joerg Roedel <jroedel@suse.de>
To: Baoquan He <bhe@redhat.com>
Cc: Joerg Roedel <joro@8bytes.org>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3 v2] Fix kdump failures with crashkernel=high
Date: Tue, 2 Jun 2015 11:08:28 +0200 [thread overview]
Message-ID: <20150602090828.GD16345@suse.de> (raw)
In-Reply-To: <20150602085401.GA31889@dhcp-128-28.nay.redhat.com>
Hi Baoquan
On Tue, Jun 02, 2015 at 04:54:01PM +0800, Baoquan He wrote:
> Ping!
>
> About this patchset, what's your plan?
Sorry, this went out of my scope. Thanks for reminding me, I'll send a
new version soon.
Joerg
prev parent reply other threads:[~2015-06-02 9:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 14:51 [PATCH 0/3 v2] Fix kdump failures with crashkernel=high Joerg Roedel
2015-01-06 14:51 ` [PATCH 1/3] swiotlb: Warn on allocation failure in swiotlb_alloc_coherent Joerg Roedel
2015-01-23 17:04 ` Borislav Petkov
2015-01-26 11:49 ` Joerg Roedel
2015-01-06 14:51 ` [PATCH 2/3] x86, swiotlb: Try coherent allocations with __GFP_NOWARN Joerg Roedel
2015-01-23 17:03 ` Borislav Petkov
2015-01-26 3:22 ` Baoquan He
2015-01-26 11:54 ` Joerg Roedel
2015-01-06 14:51 ` [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high Joerg Roedel
2015-01-23 8:44 ` Baoquan He
2015-01-26 12:07 ` Joerg Roedel
2015-02-01 8:41 ` Baoquan He
2015-02-04 14:10 ` Joerg Roedel
2015-02-09 12:20 ` Joerg Roedel
2015-02-13 15:34 ` Baoquan He
2015-02-13 22:28 ` Joerg Roedel
2015-02-14 11:44 ` Baoquan He
2015-01-23 17:02 ` Borislav Petkov
2015-01-26 12:11 ` Joerg Roedel
2015-01-26 12:20 ` Borislav Petkov
2015-01-26 12:40 ` Joerg Roedel
2015-01-26 12:45 ` Borislav Petkov
2015-01-14 13:35 ` [PATCH 0/3 v2] Fix kdump failures with crashkernel=high Joerg Roedel
2015-01-19 19:26 ` Borislav Petkov
2015-01-19 19:26 ` Borislav Petkov
2015-02-14 10:58 ` Baoquan He
2015-02-14 16:11 ` Joerg Roedel
2015-06-02 8:54 ` Baoquan He
2015-06-02 9:08 ` Joerg Roedel [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=20150602090828.GD16345@suse.de \
--to=jroedel@suse.de \
--cc=bhe@redhat.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.