On Tue, Jun 18, 2024 at 07:04:24AM +0300, Mike Rapoport wrote: > Hi Greg, > > On Mon, Jun 17, 2024 at 08:21:27PM +0200, gregkh@xxxxxxxxxxxxxxxxxxx wrote: > > > > This is a note to let you know that I've just added the patch titled > > > > x86/mm/numa: Use NUMA_NO_NODE when calling memblock_set_node() > > > > to the 5.10-stable tree which can be found at: > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary > > > > The filename of the patch is: > > x86-mm-numa-use-numa_no_node-when-calling-memblock_set_node.patch > > and it can be found in the queue-5.10 subdirectory. > > > > If you, or anyone else, feels it should not be added to the stable tree, > > please let <stable@xxxxxxxxxxxxxxx> know about it. > > > > > > From 3ac36aa7307363b7247ccb6f6a804e11496b2b36 Mon Sep 17 00:00:00 2001 > > From: Jan Beulich <jbeulich@xxxxxxxx> > > Date: Wed, 29 May 2024 09:42:05 +0200 > > Subject: x86/mm/numa: Use NUMA_NO_NODE when calling memblock_set_node() > > > > From: Jan Beulich <jbeulich@xxxxxxxx> > > > > commit 3ac36aa7307363b7247ccb6f6a804e11496b2b36 upstream. > > > > memblock_set_node() warns about using MAX_NUMNODES, see > > > > e0eec24e2e19 ("memblock: make memblock_set_node() also warn about use of MAX_NUMNODES") > > This commit was a fix for e0eec24e2e19, it's not needed for kernels before > 6.8. > Sorry I didn't note this in the commit log. No worries, thanks for letting us know, now dropped from all but the 6.9.y queue. greg k-h
