From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Thorsten Blum <thorsten.blum@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/page_alloc: Use str_off_on() helper in build_all_zonelists()
Date: Tue, 22 Oct 2024 10:37:05 +0530 [thread overview]
Message-ID: <a11f46f7-29bc-4242-bd8b-d316065607e2@arm.com> (raw)
In-Reply-To: <20241021091340.5243-2-thorsten.blum@linux.dev>
On 10/21/24 14:43, Thorsten Blum wrote:
> Remove hard-coded strings by using the str_off_on() helper function.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> mm/page_alloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 8afab64814dc..11d3fa3587db 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -5495,7 +5495,7 @@ void __ref build_all_zonelists(pg_data_t *pgdat)
>
> pr_info("Built %u zonelists, mobility grouping %s. Total pages: %ld\n",
> nr_online_nodes,
> - page_group_by_mobility_disabled ? "off" : "on",
> + str_off_on(page_group_by_mobility_disabled),
> vm_total_pages);
> #ifdef CONFIG_NUMA
> pr_info("Policy zone: %s\n", zone_names[policy_zone]);
There are multiple other instances which could use similar str_on_off() as well.
mm/kasan/hw_tags.c: kasan_vmalloc_enabled() ? "on" : "off",
mm/kasan/hw_tags.c: kasan_stack_collection_enabled() ? "on" : "off");
mm/kasan/sw_tags.c: kasan_stack_collection_enabled() ? "on" : "off");
mm/mm_init.c: stack, want_init_on_alloc(GFP_KERNEL) ? "on" : "off",
mm/mm_init.c: want_init_on_free() ? "on" : "off");
I would suggest converting all of them together in a single patch instead.
prev parent reply other threads:[~2024-10-22 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 9:13 Thorsten Blum
2024-10-22 5:07 ` Anshuman Khandual [this message]
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=a11f46f7-29bc-4242-bd8b-d316065607e2@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=thorsten.blum@linux.dev \
/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