From: Chen Zhou <chenzhou10@huawei.com>
To: Dave Young <dyoung@redhat.com>
Cc: <catalin.marinas@arm.com>, <will.deacon@arm.com>,
<akpm@linux-foundation.org>, <ard.biesheuvel@linaro.org>,
<rppt@linux.ibm.com>, <tglx@linutronix.de>, <mingo@redhat.com>,
<bp@alien8.de>, <ebiederm@xmission.com>,
<wangkefeng.wang@huawei.com>, <linux-mm@kvack.org>,
<kexec@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<takahiro.akashi@linaro.org>, <horms@verge.net.au>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/4] x86: kdump: move reserve_crashkernel_low() into kexec_core.c
Date: Thu, 13 Jun 2019 19:27:51 +0800 [thread overview]
Message-ID: <681c9884-4b8b-be87-2d78-d5f53ab23f34@huawei.com> (raw)
In-Reply-To: <20190612084551.GA24575@dhcp-128-65.nay.redhat.com>
Hi Dave,
On 2019/6/12 16:45, Dave Young wrote:
> Other than the comments from James, can you move the function into
> kernel/crash_core.c, we already have some functions moved there for
> sharing.
Sure.
Thanks,
Chen Zhou
next prev parent reply other threads:[~2019-06-13 11:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 3:50 [PATCH 0/4] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2019-05-07 3:50 ` [PATCH 1/4] x86: kdump: move reserve_crashkernel_low() into kexec_core.c Chen Zhou
2019-06-05 16:29 ` James Morse
2019-06-13 11:26 ` Chen Zhou
2019-06-12 8:45 ` Dave Young
2019-06-13 11:27 ` Chen Zhou [this message]
2019-05-07 3:50 ` [PATCH 2/4] arm64: kdump: support reserving crashkernel above 4G Chen Zhou
2019-06-05 16:29 ` James Morse
2019-06-13 11:27 ` Chen Zhou
2019-06-13 12:44 ` James Morse
2019-05-07 3:50 ` [PATCH 3/4] memblock: extend memblock_cap_memory_range to multiple ranges Chen Zhou
2019-05-07 3:50 ` [PATCH 4/4] kdump: update Documentation about crashkernel on arm64 Chen Zhou
2019-05-15 5:16 ` Bhupesh Sharma
2019-05-16 3:23 ` Chen Zhou
2019-05-15 5:06 ` [PATCH 0/4] support reserving crashkernel above 4G on arm64 kdump Bhupesh Sharma
2019-05-16 3:19 ` Chen Zhou
2019-06-03 2:24 ` Chen Zhou
2019-06-05 16:32 ` James Morse
2019-06-13 11:27 ` Chen Zhou
2019-06-13 12:43 ` James Morse
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=681c9884-4b8b-be87-2d78-d5f53ab23f34@huawei.com \
--to=chenzhou10@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=rppt@linux.ibm.com \
--cc=takahiro.akashi@linaro.org \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.com \
--cc=will.deacon@arm.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