All of
 help / color / mirror / Atom feed
Subject: + x86-kconfig-introduce-arch_mhp_memmap_on_memory_enable.patch added to -mm tree
Date: Wed, 10 Mar 2021 16:51:04 -0800	[thread overview]
Message-ID: <> (raw)

The patch titled
     Subject: x86/Kconfig: introduce ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
has been added to the -mm tree.  Its filename is

This patch should soon appear at
and later at

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***

The -mm tree is included into linux-next and is updated
there every 3-4 working days

From: Oscar Salvador <>
Subject: x86/Kconfig: introduce ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE

Enable x86_64 platform to use the MHP_MEMMAP_ON_MEMORY feature.

Signed-off-by: Oscar Salvador <>
Reviewed-by: David Hildenbrand <>
Cc: Anshuman Khandual <>
Cc: Michal Hocko <>
Cc: Pavel Tatashin <>
Cc: Vlastimil Babka <>
Signed-off-by: Andrew Morton <>

 arch/x86/Kconfig |    3 +++
 1 file changed, 3 insertions(+)

--- a/arch/x86/Kconfig~x86-kconfig-introduce-arch_mhp_memmap_on_memory_enable
+++ a/arch/x86/Kconfig
@@ -2434,6 +2434,9 @@ config ARCH_ENABLE_MEMORY_HOTREMOVE
 	def_bool y
 	depends on MEMORY_HOTPLUG
+	def_bool y
 	def_bool y
 	depends on NUMA

Patches currently in -mm which might be from are


             reply	other threads:[~2021-03-11  0:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  0:51 akpm [this message]
2021-03-19 16:47 + x86-kconfig-introduce-arch_mhp_memmap_on_memory_enable.patch added to -mm tree akpm
2021-04-16 18:48 akpm
2021-04-16 19:56 akpm
2021-04-22  4:24 akpm

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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.