From: Mike Rapoport <rppt@kernel.org>
To: Borislav Petkov <bp@kernel.org>, Jan Beulich <jbeulich@suse.com>
Cc: 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: Thu, 6 Jun 2024 17:37:49 +0300 [thread overview]
Message-ID: <ZmHJvY5h887hDN87@kernel.org> (raw)
In-Reply-To: <171750701353.925406.16431237983148253122.b4-ty@kernel.org>
On Tue, Jun 04, 2024 at 04:16:57PM +0300, Mike Rapoport wrote:
> 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
There was a similar, but better fix from Jan Beulich:
https://lore.kernel.org/lkml/abadb736-a239-49e4-ab42-ace7acdd4278@suse.com/
that also updated numa_clear_kernel_node_hotplug().
I'm going to replace this patch with his and use Boris' changelog as more
appropriate.
> --
> Sincerely yours,
> Mike.
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2024-06-06 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 14:10 [PATCH] x86/mm/numa: Use NUMA_NO_NODE when calling memblock_set_node() Borislav Petkov
2024-06-03 14:25 ` Mike Rapoport
2024-06-04 13:16 ` Mike Rapoport
2024-06-06 14:37 ` 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=ZmHJvY5h887hDN87@kernel.org \
--to=rppt@kernel.org \
--cc=Narasimhan.V@amd.com \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.