From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, anshuman.khandual@arm.com,
mm-commits@vger.kernel.org, osalvador@suse.de,
sfr@canb.auug.org.au
Subject: [folded-merged] mm-drop-redundant-arch_enable__migration-fix.patch removed from -mm tree
Date: Tue, 04 May 2021 17:57:50 -0700 [thread overview]
Message-ID: <20210505005750.UcjRZq60K%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm-drop-redundant-arch_enable__migration-fix
has been removed from the -mm tree. Its filename was
mm-drop-redundant-arch_enable__migration-fix.patch
This patch was dropped because it was folded into mm-drop-redundant-arch_enable__migration.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-drop-redundant-arch_enable__migration-fix
s/x86_64/X86_64/, per Oscar
Cc: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Oscar Salvador <osalvador@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/x86/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/arch/x86/Kconfig~mm-drop-redundant-arch_enable__migration-fix
+++ a/arch/x86/Kconfig
@@ -60,7 +60,7 @@ config X86
select ACPI_SYSTEM_POWER_STATES_SUPPORT if ACPI
select ARCH_32BIT_OFF_T if X86_32
select ARCH_CLOCKSOURCE_INIT
- select ARCH_ENABLE_HUGEPAGE_MIGRATION if x86_64 && HUGETLB_PAGE && MIGRATION
+ select ARCH_ENABLE_HUGEPAGE_MIGRATION if X86_64 && HUGETLB_PAGE && MIGRATION
select ARCH_ENABLE_MEMORY_HOTPLUG if X86_64 || (X86_32 && HIGHMEM)
select ARCH_ENABLE_MEMORY_HOTREMOVE if MEMORY_HOTPLUG
select ARCH_ENABLE_THP_MIGRATION if x86_64 && TRANSPARENT_HUGEPAGE
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-drop-redundant-arch_enable__migration.patch
mm-drop-redundant-arch_enable__migration-fix-fix.patch
mm.patch
kernel-resource-allow-region_intersects-users-to-hold-resource_lock-fix.patch
linux-next-rejects.patch
cifsd-is-broken.patch
kernel-forkc-export-kernel_thread-to-modules.patch
reply other threads:[~2021-05-05 0:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210505005750.UcjRZq60K%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=sfr@canb.auug.org.au \
/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.