From: "Rob Herring (Arm)" <robh@kernel.org>
To: Sang-Heon Jeon <ekffu200098@gmail.com>
Cc: devicetree@vger.kernel.org, saravanak@kernel.org
Subject: Re: [PATCH] of/fdt: remove redundant memset in __unflatten_device_tree()
Date: Tue, 21 Apr 2026 14:34:53 -0500 [thread overview]
Message-ID: <177679993172.1520888.14733708891951658401.robh@kernel.org> (raw)
In-Reply-To: <20260418140420.2221736-1-ekffu200098@gmail.com>
On Sat, 18 Apr 2026 23:04:20 +0900, Sang-Heon Jeon wrote:
> All dt_alloc callbacks passed to __unflatten_device_tree() already
> return zero-initialized memory.
>
> - kernel_tree_alloc uses kzalloc()
> - early_init_dt_alloc_memory_arch() and dt_alloc_memory() both use
> memblock_alloc()
>
> So remove redundant memset after the allocation. No funtional change.
That is true now, but it wasn't the case before memblock became used on
all arches.
I've updated the commit message with this info and applied.
Rob
next prev parent reply other threads:[~2026-04-21 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 14:04 [PATCH] of/fdt: remove redundant memset in __unflatten_device_tree() Sang-Heon Jeon
2026-04-21 19:34 ` Rob Herring (Arm) [this message]
2026-04-21 22:40 ` Sang-Heon Jeon
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=177679993172.1520888.14733708891951658401.robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ekffu200098@gmail.com \
--cc=saravanak@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