From: Wandun Chen <chenwandun1@gmail.com>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
zhaomeijing@lixiang.com
Cc: robh@kernel.org, saravanak@kernel.org
Subject: [PATCH v2 0/3] of: reserved_mem: fixes and cleanups
Date: Tue, 19 May 2026 16:24:24 +0800 [thread overview]
Message-ID: <20260519082427.4181476-1-chenwandun@lixiang.com> (raw)
This is v2 of the OF reserved memory fixes/cleanups series.
The original v1 [1] contains two parts of work:
- Bug fixes and small cleanups about reserved memory.
- A vmcore size optimization that exclude reserved memory out of
vmcore.
For the convenience of review, I have split it into two independent
patchsets. This patchset only contains bug fixes and cleanups
content, while the content optimized for vmcore size will be in
another patchset.
v1 --> v2:
1. Add new patch 1, to fix unnecessary memory allocation.
2. Support only one entry in reg property in patch 3, suggested by
Rob Herring [2].
3. Per Rob's review on v1 2/11 [3], drop patch about "rejecting
reserved memory outside physical memory range" due to potential
abuse.
4. Drop patch about "of: reserved_mem: avoid unconditional save of
reg entries in fdt_scan_reserved_mem_late()" due to a
misunderstanding on my side.
5. Update commit message.
[1] https://lore.kernel.org/lkml/20260429065831.1510858-1-chenwandun@lixiang.com/
[2] https://lore.kernel.org/all/20260429065831.1510858-1-chenwandun@lixiang.com/T/#m29fa0f1c22c23e6343070e70f905c9482f930901
[3] https://lore.kernel.org/all/20260429065831.1510858-1-chenwandun@lixiang.com/T/#m5948f8679540fb361e7f432137babb4609ff154f
Wandun Chen (3):
of: reserved_mem: avoid unnecessary memory allocation when
__reserved_mem_check_root() fails
of: reserved_mem: clean up redundant alloc_reserved_mem_array() call
of: reserved_mem: only support one <base size> entry in reg property
drivers/of/of_reserved_mem.c | 48 +++++++++++++++++++++---------------
1 file changed, 28 insertions(+), 20 deletions(-)
--
2.43.0
next reply other threads:[~2026-05-19 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 8:24 Wandun Chen [this message]
2026-05-19 8:24 ` [PATCH v2 1/3] of: reserved_mem: avoid unnecessary memory allocation when __reserved_mem_check_root() fails Wandun Chen
2026-05-20 7:44 ` Krzysztof Kozlowski
2026-05-20 8:16 ` Wandun
2026-06-01 23:06 ` Rob Herring
2026-06-02 1:37 ` Wandun
2026-05-19 8:24 ` [PATCH v2 2/3] of: reserved_mem: clean up redundant alloc_reserved_mem_array() call Wandun Chen
2026-05-19 8:24 ` [PATCH v2 3/3] of: reserved_mem: only support one <base size> entry in reg property Wandun Chen
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=20260519082427.4181476-1-chenwandun@lixiang.com \
--to=chenwandun1@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@kernel.org \
--cc=zhaomeijing@lixiang.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
all inboxes | Powered by JetHome®