From: Vlastimil Babka <vbabka@suse.cz>
To: Manish Kumar <manish1588@gmail.com>, akpm@linux-foundation.org
Cc: surenb@google.com, mhocko@suse.com, jackmanb@google.com,
hannes@cmpxchg.org, ziy@nvidia.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/show_mem: update printk/pr_info messages and replace legacy printk(KERN_CONT ...) with pr_cont()
Date: Fri, 19 Sep 2025 08:46:05 +0200 [thread overview]
Message-ID: <e8121724-a436-47d5-af3a-a16f81cd0649@suse.cz> (raw)
In-Reply-To: <20250918181403.93812-1-manish1588@gmail.com>
Changelog should not be empty even for trivial patches.
On 9/18/25 20:14, Manish Kumar wrote:
> Signed-off-by: Manish Kumar <manish1588@gmail.com>
This changes 2 of X in the file. Why only these 2? And no, I'm not
encouraging to resend with a full file changes. We do these modernizations
to new APIs only while changing the code for other reasons, not separately,
if there's nothing wrong otherwise with the legacy api. The churn isn't
worth it.
> ---
> mm/show_mem.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/show_mem.c b/mm/show_mem.c
> index 0cf8bf5d832d..798949d10ce1 100644
> --- a/mm/show_mem.c
> +++ b/mm/show_mem.c
> @@ -26,7 +26,7 @@ unsigned long totalcma_pages __read_mostly;
> static inline void show_node(struct zone *zone)
> {
> if (IS_ENABLED(CONFIG_NUMA))
> - printk("Node %d ", zone_to_nid(zone));
> + pr_info("Node %d ", zone_to_nid(zone));
> }
>
> long si_mem_available(void)
> @@ -156,7 +156,7 @@ static void show_migration_types(unsigned char type)
> }
>
> *p = '\0';
> - printk(KERN_CONT "(%s) ", tmp);
> + pr_cont("(%s) ", tmp);
> }
>
> static bool node_has_managed_zones(pg_data_t *pgdat, int max_zone_idx)
next prev parent reply other threads:[~2025-09-19 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 18:14 Manish Kumar
2025-09-19 6:46 ` Vlastimil Babka [this message]
2025-09-19 16:18 ` Manish Kumar
2025-09-19 16:40 ` Manish Kumar
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=e8121724-a436-47d5-af3a-a16f81cd0649@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manish1588@gmail.com \
--cc=mhocko@suse.com \
--cc=surenb@google.com \
--cc=ziy@nvidia.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