aboutsummaryrefslogtreecommitdiff
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorGravatar Linus Torvalds <torvalds@linux-foundation.org> 2024-06-13 10:09:29 -0700
committerGravatar Linus Torvalds <torvalds@linux-foundation.org> 2024-06-13 10:09:29 -0700
commit3572597ca844f625a3c9ba629ed0872b64c16179 (patch)
treebed719dc9309aa9734faf1c7776513f007518133 /MAINTAINERS
parentMerge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rmk/linux (diff)
parentx86/mm/numa: Use NUMA_NO_NODE when calling memblock_set_node() (diff)
downloadlinux-3572597ca844f625a3c9ba629ed0872b64c16179.tar.gz
linux-3572597ca844f625a3c9ba629ed0872b64c16179.tar.bz2
linux-3572597ca844f625a3c9ba629ed0872b64c16179.zip
Merge tag 'fixes-2024-06-13' of git://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
Pull memblock fixes from Mike Rapoport: "Fix validation of NUMA coverage. memblock_validate_numa_coverage() was checking for a unset node ID using NUMA_NO_NODE, but x86 used MAX_NUMNODES when no node ID was specified by buggy firmware. Update memblock to substitute MAX_NUMNODES with NUMA_NO_NODE in memblock_set_node() and use NUMA_NO_NODE in x86::numa_init()" * tag 'fixes-2024-06-13' of git://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock: x86/mm/numa: Use NUMA_NO_NODE when calling memblock_set_node() memblock: make memblock_set_node() also warn about use of MAX_NUMNODES
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions