From: Pingfan Liu <kernelfans@gmail.com>
To: devicetree@vger.kernel.org, linux-efi@vger.kernel.org
Cc: Pingfan Liu <kernelfans@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Zhen Lei <thunder.leizhen@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Frank Rowand <frowand.list@gmail.com>,
Ard Biesheuvel <ardb@kernel.org>, Nick Terrell <terrelln@fb.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/2] arm64: fdt: fix membock add/cap ordering
Date: Tue, 14 Dec 2021 12:01:55 +0800 [thread overview]
Message-ID: <20211214040157.27443-1-kernelfans@gmail.com> (raw)
In fact, V2 tackles this issue at efi_init() for both arm64 and risc-v.
Since in Zhen Lei's series "[PATCH v17 00/10] support reserving
crashkernel above 4G on arm64 kdump", [8/10] is self-standing and
meaningful. I abstract and utilize it.
I make a small change in it in order to use
early_init_dt_check_for_usable_mem_range() outside of/fdt.
(Cc: Zhen, please let me know if it is not fine for you.)
So finally these two patches can be applied as candidates for
Fixes: b261dba2fdb2 ("arm64: kdump: Remove custom linux,usable-memory-range handling")
[1]: https://lore.kernel.org/all/20211210065533.2023-9-thunder.leizhen@huawei.com/
v1 -> v2:
Adopt Rob's suggestion to call
early_init_dt_check_for_usable_mem_range() from efi_init()
Cc: Rob Herring <robh+dt@kernel.org>
Cc: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Mike Rapoport <rppt@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Frank Rowand <frowand.list@gmail.com>
Cc: Ard Biesheuvel <ardb@kernel.org>
Cc: Nick Terrell <terrelln@fb.com>
Cc: linux-arm-kernel@lists.infradead.org
To: devicetree@vger.kernel.org
To: linux-efi@vger.kernel.org
Pingfan Liu (1):
efi: apply memblock cap after memblock_add()
Zhen Lei (1):
of: fdt: Aggregate the processing of "linux,usable-memory-range"
drivers/firmware/efi/efi-init.c | 7 +++++++
drivers/of/fdt.c | 18 +++++++++++++-----
include/linux/of_fdt.h | 1 +
3 files changed, 21 insertions(+), 5 deletions(-)
--
2.31.1
next reply other threads:[~2021-12-14 4:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 4:01 Pingfan Liu [this message]
2021-12-14 4:01 ` [PATCHv2 1/2] of: fdt: Aggregate the processing of "linux,usable-memory-range" Pingfan Liu
2021-12-14 4:01 ` [PATCHv2 2/2] efi: apply memblock cap after memblock_add() Pingfan Liu
2021-12-14 14:55 ` Rob Herring
2021-12-15 2:04 ` Pingfan Liu
2021-12-15 2:13 ` [PATCHv3] " Pingfan Liu
2021-12-15 3:58 ` Leizhen (ThunderTown)
2021-12-15 5:29 ` Pingfan Liu
2021-12-15 6:53 ` Leizhen (ThunderTown)
2021-12-15 8:24 ` Pingfan Liu
2021-12-15 15:05 ` Rob Herring
2021-12-16 13:34 ` Leizhen (ThunderTown)
2021-12-17 15:08 ` Rob Herring
2021-12-17 15:25 ` Ard Biesheuvel
2021-12-21 15:17 ` Rob Herring
2021-12-22 8:00 ` Leizhen (ThunderTown)
2021-12-23 7:33 ` Leizhen (ThunderTown)
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=20211214040157.27443-1-kernelfans@gmail.com \
--to=kernelfans@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rppt@kernel.org \
--cc=terrelln@fb.com \
--cc=thunder.leizhen@huawei.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).