[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YaagJQqq2Cx2zyVw@robh.at.kernel.org>
Date: Tue, 30 Nov 2021 16:05:25 -0600
From: Rob Herring <robh@...nel.org>
To: Zhen Lei <thunder.leizhen@...wei.com>
Cc: Vivek Goyal <vgoyal@...hat.com>,
Chen Zhou <dingguo.cz@...group.com>,
Frank Rowand <frowand.list@...il.com>,
linux-doc@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
devicetree@...r.kernel.org,
Catalin Marinas <catalin.marinas@....com>,
Eric Biederman <ebiederm@...ssion.com>,
Feng Zhou <zhoufeng.zf@...edance.com>,
"H . Peter Anvin" <hpa@...or.com>,
Jonathan Corbet <corbet@....net>,
Rob Herring <robh+dt@...nel.org>, linux-kernel@...r.kernel.org,
Borislav Petkov <bp@...en8.de>, x86@...nel.org,
Randy Dunlap <rdunlap@...radead.org>,
Baoquan He <bhe@...hat.com>, kexec@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
Kefeng Wang <wangkefeng.wang@...wei.com>,
Will Deacon <will@...nel.org>, Dave Young <dyoung@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v16 09/11] of: fdt: Aggregate the processing of
"linux,usable-memory-range"
On Tue, 23 Nov 2021 20:46:44 +0800, Zhen Lei wrote:
> Currently, we parse the "linux,usable-memory-range" property in
> early_init_dt_scan_chosen(), to obtain the specified memory range of the
> crash kernel. We then reserve the required memory after
> early_init_dt_scan_memory() has identified all available physical memory.
> Because the two pieces of code are separated far, the readability and
> maintainability are reduced. So bring them together.
>
> Suggested-by: Rob Herring <robh@...nel.org>
> Signed-off-by: Zhen Lei <thunder.leizhen@...wei.com>
> ---
> drivers/of/fdt.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists