linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Manish Kumar <manish1588@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: akpm@linux-foundation.org, 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 21:48:17 +0530	[thread overview]
Message-ID: <CAAoxDjeUyKs2xN4oBRWnZBWvGLoi4v+nT7ioYVQtB9B2hRj5yw@mail.gmail.com> (raw)
In-Reply-To: <e8121724-a436-47d5-af3a-a16f81cd0649@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

Hi,

Thanks for the feedback. I understand now that printk→pr_* cleanups are not
accepted as standalone cosmetic patches. I will drop this patch and focus
on patches with real fixes.

Best regards,
Manish Kumar

On Fri, Sep 19, 2025 at 12:16 PM Vlastimil Babka <vbabka@suse.cz> wrote:

> 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)
>
>

[-- Attachment #2: Type: text/html, Size: 2283 bytes --]

  reply	other threads:[~2025-09-19 16:18 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
2025-09-19 16:18   ` Manish Kumar [this message]
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=CAAoxDjeUyKs2xN4oBRWnZBWvGLoi4v+nT7ioYVQtB9B2hRj5yw@mail.gmail.com \
    --to=manish1588@gmail.com \
    --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=mhocko@suse.com \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --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