Received-SPF: pass (google.com: domain of linux-kernel+bounces-200684-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: Mike Rapoport <rppt@kernel.org>
To: Borislav Petkov <bp@kernel.org>
Cc: Mike Rapoport <rppt@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	Narasimhan V <Narasimhan.V@amd.com>
Subject: Re: [PATCH] x86/mm/numa: Use NUMA_NO_NODE when calling memblock_set_node()
Date: Tue,  4 Jun 2024 16:16:57 +0300
Message-ID: <171750701353.925406.16431237983148253122.b4-ty@kernel.org>
In-Reply-To: <20240603141005.23261-1-bp@kernel.org>
References: <20240603141005.23261-1-bp@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

From: Mike Rapoport (IBM) <rppt@kernel.org>

On Mon, 03 Jun 2024 16:10:05 +0200, Borislav Petkov wrote:
> memblock_set_node() warns about using MAX_NUMNODES, see
> 
>   e0eec24e2e19 ("memblock: make memblock_set_node() also warn about use of MAX_NUMNODES")
> 
> for details.
> 
> 
> [...]

Applied to fixes branch of memblock.git tree, thanks!

[1/1] x86/mm/numa: Use NUMA_NO_NODE when calling memblock_set_node()
      commit: c55f3cc2d9f241d6e45336fd48dafa755c012297

tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
branch: fixes

--
Sincerely yours,
Mike.