From: Will Deacon <will@kernel.org>
To: John Donnelly <John.P.donnelly@oracle.com>
Cc: horms@verge.net.au, devicetree@vger.kernel.org, arnd@arndb.de,
Baoquan He <bhe@redhat.com>,
linux-doc@vger.kernel.org, Chen Zhou <chenzhou10@huawei.com>,
catalin.marinas@arm.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
mingo@redhat.com, james.morse@arm.com, guohanjun@huawei.com,
tglx@linutronix.de, pkushwaha@marvell.com, dyoung@redhat.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 0/5] support reserving crashkernel above 4G on arm64 kdump
Date: Fri, 29 May 2020 09:05:39 +0100 [thread overview]
Message-ID: <20200529080539.GC4351@willie-the-truck> (raw)
In-Reply-To: <897ea1b9-a68c-8544-6532-a21be135ce01@oracle.com>
[+James Morse]
On Thu, May 28, 2020 at 05:20:34PM -0500, John Donnelly wrote:
> On 5/25/20 8:42 PM, Baoquan He wrote:
> > On 05/21/20 at 05:38pm, Chen Zhou wrote:
> > > This patch series enable reserving crashkernel above 4G in arm64.
[...]
> > > Chen Zhou (5):
> > > x86: kdump: move reserve_crashkernel_low() into crash_core.c
> > > arm64: kdump: reserve crashkenel above 4G for crash dump kernel
> > > arm64: kdump: add memory for devices by DT property, low-memory-range
> > > kdump: update Documentation about crashkernel on arm64
> > > dt-bindings: chosen: Document linux,low-memory-range for arm64 kdump
> > >
> > > Documentation/admin-guide/kdump/kdump.rst | 13 ++-
> > > .../admin-guide/kernel-parameters.txt | 12 ++-
> > > Documentation/devicetree/bindings/chosen.txt | 25 ++++++
> > > arch/arm64/kernel/setup.c | 8 +-
> > > arch/arm64/mm/init.c | 61 ++++++++++++-
> > > arch/x86/kernel/setup.c | 66 ++------------
> > > include/linux/crash_core.h | 3 +
> > > include/linux/kexec.h | 2 -
> > > kernel/crash_core.c | 85 +++++++++++++++++++
> > > kernel/kexec_core.c | 17 ----
> > > 10 files changed, 208 insertions(+), 84 deletions(-)
> > >
> This proposal to improve vmcore creation on Arm has been going on for
> almost a year now.
>
> Who is the final maintainer that needs to approve and except these ?
>
> What are the lingering issues that are remaining so we get these accepted
> into a upstream commit ?
The arm64 bits need an Ack from James Morse, but he's not on CC despite
offering feedback on earlier versions.
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-29 8:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 9:38 [PATCH v8 0/5] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2020-05-21 9:38 ` [PATCH v8 1/5] x86: kdump: move reserve_crashkernel_low() into crash_core.c Chen Zhou
2020-05-26 0:56 ` Baoquan He
2020-05-21 9:38 ` [PATCH v8 2/5] arm64: kdump: reserve crashkenel above 4G for crash dump kernel Chen Zhou
2020-05-26 0:59 ` Baoquan He
2020-05-21 9:38 ` [PATCH v8 3/5] arm64: kdump: add memory for devices by DT property, low-memory-range Chen Zhou
2020-05-21 9:38 ` [PATCH v8 4/5] kdump: update Documentation about crashkernel on arm64 Chen Zhou
2020-05-21 9:38 ` [PATCH v8 5/5] dt-bindings: chosen: Document linux, low-memory-range for arm64 kdump Chen Zhou
2020-05-21 13:29 ` Rob Herring
2020-05-22 3:24 ` [PATCH v8 5/5] dt-bindings: chosen: Document linux,low-memory-range " chenzhou
2020-05-26 21:18 ` Rob Herring
2020-05-29 16:11 ` James Morse
2020-06-20 3:54 ` chenzhou
2020-05-26 1:42 ` [PATCH v8 0/5] support reserving crashkernel above 4G on " Baoquan He
2020-05-26 2:28 ` chenzhou
2020-05-28 22:20 ` John Donnelly
2020-05-29 8:05 ` Will Deacon [this message]
2020-06-01 12:02 ` Prabhakar Kushwaha
2020-06-01 19:30 ` John Donnelly
2020-06-01 21:02 ` Bhupesh Sharma
2020-06-01 21:59 ` John Donnelly
2020-06-02 5:38 ` Prabhakar Kushwaha
2020-06-02 14:41 ` John Donnelly
2020-06-03 11:47 ` Prabhakar Kushwaha
2020-06-03 13:20 ` chenzhou
2020-06-03 15:30 ` John Donnelly
2020-06-03 19:47 ` Bhupesh Sharma
2020-06-04 7:14 ` Will Deacon
2020-06-04 17:01 ` Nicolas Saenz Julienne
2020-06-05 2:26 ` John Donnelly
2020-06-05 8:21 ` Nicolas Saenz Julienne
2020-06-19 2:32 ` John Donnelly
2020-06-19 8:21 ` chenzhou
2020-06-20 0:01 ` John Donnelly
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=20200529080539.GC4351@willie-the-truck \
--to=will@kernel.org \
--cc=John.P.donnelly@oracle.com \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=chenzhou10@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=dyoung@redhat.com \
--cc=guohanjun@huawei.com \
--cc=horms@verge.net.au \
--cc=james.morse@arm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pkushwaha@marvell.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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