From: "Cheatham, Benjamin" <benjamin.cheatham@amd.com>
To: Gregory Price <gourry@gourry.net>, <linux-mm@kvack.org>
Cc: <linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel-team@meta.com>, <david@kernel.org>, <osalvador@suse.de>,
<gregkh@linuxfoundation.org>, <rafael@kernel.org>,
<dakr@kernel.org>, <akpm@linux-foundation.org>,
<lorenzo.stoakes@oracle.com>, <Liam.Howlett@oracle.com>,
<vbabka@suse.cz>, <rppt@kernel.org>, <surenb@google.com>,
<mhocko@suse.com>, Jonathan Cameron <jonathan.cameron@huawei.com>
Subject: Re: [PATCH] mm: name the anonymous MMOP enum as enum mmop
Date: Wed, 11 Feb 2026 16:18:45 -0600 [thread overview]
Message-ID: <35db57ae-64cd-40ed-8353-7d3b64069471@amd.com> (raw)
In-Reply-To: <20260211215447.2194189-1-gourry@gourry.net>
On 2/11/2026 3:54 PM, Gregory Price wrote:
> Give the MMOP enum (MMOP_OFFLINE, MMOP_ONLINE, etc) a proper type
> name so the compiler can help catch invalid values being assigned to
> variables of this type.
>
> Leave the existing functions returning int alone to allow for
> value-or-error pattern to remain unchanged without churn.
>
> mmop_default_online_type is left as int because it uses the -1
> sentinal value to signal it hasn't been initialized yet.
>
> Keep the uint8_t buffer in offline_and_remove_memory() as-is for
> space efficiency, with an explicit cast when we consume the value.
>
> Move the enum definition before the CONFIG_MEMORY_HOTPLUG guard so
> it is unconditionally available for struct memory_block in memory.h.
>
> No functional change.
>
> Link: https://lore.kernel.org/linux-mm/3424eba7-523b-4351-abd0-3a888a3e5e61@kernel.org/
> Suggested-by: Jonathan Cameron <jonathan.cameron@huawei.com>
> Suggested-by: "David Hildenbrand (arm)" <david@kernel.org>
> Signed-off-by: Gregory Price <gourry@gourry.net>
> ---
I saw this when reviewing another set of yours and thought about mentioning it, glad you cleaned it up!
One small nit below, otherwise:
Reviewed-by: Ben Cheatham <benjamin.cheatham@amd.com>
> drivers/base/memory.c | 2 +-
> include/linux/memory.h | 3 ++-
> include/linux/memory_hotplug.h | 16 ++++++++--------
> mm/memory_hotplug.c | 10 +++++-----
> 4 files changed, 16 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/base/memory.c b/drivers/base/memory.c
> index 751f248ca4a8..3753ca80069d 100644
> --- a/drivers/base/memory.c
> +++ b/drivers/base/memory.c
> @@ -452,7 +452,7 @@ static ssize_t phys_device_show(struct device *dev,
> static int print_allowed_zone(char *buf, int len, int nid,
> struct memory_group *group,
> unsigned long start_pfn, unsigned long nr_pages,
> - int online_type, struct zone *default_zone)
> + enum mmop online_type, struct zone *default_zone)
> {
> struct zone *zone;
>
> diff --git a/include/linux/memory.h b/include/linux/memory.h
> index faeaa921e55b..5bb5599c6b2b 100644
> --- a/include/linux/memory.h
> +++ b/include/linux/memory.h
> @@ -19,6 +19,7 @@
> #include <linux/node.h>
> #include <linux/compiler.h>
> #include <linux/mutex.h>
> +#include <linux/memory_hotplug.h>
>
> #define MIN_MEMORY_BLOCK_SIZE (1UL << SECTION_SIZE_BITS)
>
> @@ -77,7 +78,7 @@ enum memory_block_state {
> struct memory_block {
> unsigned long start_section_nr;
> enum memory_block_state state; /* serialized by the dev->lock */
> - int online_type; /* for passing data to online routine */
> + enum mmop online_type; /* for passing data to online routine */
Comment looks unaligned.
Thanks,
Ben
next prev parent reply other threads:[~2026-02-11 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 21:54 Gregory Price
2026-02-11 22:18 ` Cheatham, Benjamin [this message]
2026-02-12 16:33 ` Gregory Price
2026-02-12 8:56 ` David Hildenbrand (Arm)
2026-02-12 16:03 ` Dave Jiang
2026-02-12 18:13 ` Davidlohr Bueso
2026-02-19 11:18 ` Jonathan Cameron
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=35db57ae-64cd-40ed-8353-7d3b64069471@amd.com \
--to=benjamin.cheatham@amd.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dakr@kernel.org \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=gregkh@linuxfoundation.org \
--cc=jonathan.cameron@huawei.com \
--cc=kernel-team@meta.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=rafael@kernel.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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