linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: willy@infradead.org, andriy.shevchenko@linux.intel.com,
	david@redhat.com, linmiaohe@huawei.com, vbabka@suse.cz,
	cl@linux.com, penberg@kernel.org, rientjes@google.com,
	iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
	rostedt@goodmis.org, sergey.senozhatsky@gmail.com,
	joe@perches.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] vsprintf: dump full information of page flags in pGp fix
Date: Tue, 23 Feb 2021 15:49:22 +0100	[thread overview]
Message-ID: <YDUV8kqgK0fCgpOf@alley> (raw)
In-Reply-To: <20210223055124.75882-1-laoar.shao@gmail.com>

On Tue 2021-02-23 13:51:24, Yafang Shao wrote:
> The name of the flag should be printed using default_str_spec.
> There's no difference in the output after this change because the string is
> printed as-is with both default_dec_spec and default_flag_spec.
> 
> This patch is a followup of the patchset
> "mm, vsprintf: dump full information of page flags in pGp" [1]
> 
> [1]. https://lore.kernel.org/linux-mm/20210215155141.47432-1-laoar.shao@gmail.com/
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> Cc: Petr Mladek <pmladek@suse.com>
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Cc: Vlastimil Babka <vbabka@suse.cz>
> Cc: Miaohe Lin <linmiaohe@huawei.com>
> Cc: Joe Perches <joe@perches.com>
> Cc: David Hildenbrand <david@redhat.com>

Reviewed-by: Petr Mladek <pmladek@suse.com>

Best Regards,
Petr


  reply	other threads:[~2021-02-23 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23  5:51 [PATCH 1/1] vsprintf: dump full information of page flags in pGp fix Yafang Shao
2021-02-23 14:49 ` Petr Mladek [this message]
2021-03-09 10:22 ` Petr Mladek

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=YDUV8kqgK0fCgpOf@alley \
    --to=pmladek@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=cl@linux.com \
    --cc=david@redhat.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=joe@perches.com \
    --cc=laoar.shao@gmail.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).