From: Meijing Zhao <zhaomeijing100@gmail.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Wandun Chen <chenwandun@lixiang.com>
Subject: Re: [PATCH v2 RESEND 2/3] mm: memblock: show all region flags in debugfs
Date: Tue, 25 Aug 2026 09:56:50 +0800 [thread overview]
Message-ID: <20260825015650.205656-1-zhaomeijing100@gmail.com> (raw)
In-Reply-To: <aoxgAYXqXvs0GFYM@kernel.org>
On Sun, Aug 23, 2026, Mike Rapoport wrote:
> first and flags can be declared here.
Agreed. I'll move them into the reg->flags block.
> Can we really have both j < count and !flagname[j]?
No. All currently defined memblock flag bits are contiguous and every
entry in flagname[] is initialized. I'll remove the redundant NULL
check.
> No need to change this
Agreed. I'll keep the existing code unchanged.
Thanks for the review.
next prev parent reply other threads:[~2026-08-25 1:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 2:09 [PATCH v2 RESEND 0/3] mm: memblock: fix debugfs flag reporting and synchronization Meijing Zhao
2026-08-21 2:09 ` [PATCH v2 RESEND 1/3] mm: memblock: add missing HugeTLB flag name Meijing Zhao
2026-08-21 2:09 ` [PATCH v2 RESEND 2/3] mm: memblock: show all region flags in debugfs Meijing Zhao
2026-08-24 15:15 ` Mike Rapoport
2026-08-25 1:56 ` Meijing Zhao [this message]
2026-08-21 2:09 ` [PATCH v2 RESEND 3/3] mm: memblock: synchronize debugfs reads with memory hotplug Meijing Zhao
2026-08-23 14:43 ` [PATCH v2 RESEND 0/3] mm: memblock: fix debugfs flag reporting and synchronization Mike Rapoport
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=20260825015650.205656-1-zhaomeijing100@gmail.com \
--to=zhaomeijing100@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chenwandun@lixiang.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@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