public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/memblock: Add MEMBLOCK_RSRV_NOINIT into flagname[] array
Date: Sun, 11 Feb 2024 10:30:56 +0200	[thread overview]
Message-ID: <ZciFwCU9kz7Uko9j@kernel.org> (raw)
In-Reply-To: <20240209030912.1382251-1-anshuman.khandual@arm.com>

On Fri, Feb 09, 2024 at 08:39:12AM +0530, Anshuman Khandual wrote:
> The commit 77e6c43e137c ("memblock: introduce MEMBLOCK_RSRV_NOINIT flag")
> skipped adding this newly introduced memblock flag into flagname[] array,
> thus preventing a correct memblock flags output for applicable memblock
> regions.
> 
> Cc: Mike Rapoport <rppt@kernel.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: linux-mm@kvack.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>

Fixes: 77e6c43e137c ("memblock: introduce MEMBLOCK_RSRV_NOINIT flag")
Reviewed-by: Mike Rapoport (IBM) <rppt@kernel.org>

> ---
> This applies on v6.8-rc3
> 
>  mm/memblock.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 4dcb2ee35eca..d9f4b82cbffe 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -2249,6 +2249,7 @@ static const char * const flagname[] = {
>  	[ilog2(MEMBLOCK_MIRROR)] = "MIRROR",
>  	[ilog2(MEMBLOCK_NOMAP)] = "NOMAP",
>  	[ilog2(MEMBLOCK_DRIVER_MANAGED)] = "DRV_MNG",
> +	[ilog2(MEMBLOCK_RSRV_NOINIT)] = "RSV_NIT",
>  };
>  
>  static int memblock_debug_show(struct seq_file *m, void *private)
> -- 
> 2.25.1
> 

-- 
Sincerely yours,
Mike.

      reply	other threads:[~2024-02-11  8:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09  3:09 [PATCH] mm/memblock: Add MEMBLOCK_RSRV_NOINIT into flagname[] array Anshuman Khandual
2024-02-11  8:30 ` Mike Rapoport [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=ZciFwCU9kz7Uko9j@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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