From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, baolin.wang@linux.alibaba.com,
akpm@linux-foundation.org, akpm@linux-foundation.org
Subject: [folded-merged] mm-rmap-fix-cont-pte-pmd-size-hugetlb-issue-when-migration-fix.patch removed from -mm tree
Date: Fri, 13 May 2022 15:34:41 -0700 [thread overview]
Message-ID: <20220513223441.C8369C34100@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-rmap-fix-cont-pte-pmd-size-hugetlb-issue-when-migration-fix
has been removed from the -mm tree. Its filename was
mm-rmap-fix-cont-pte-pmd-size-hugetlb-issue-when-migration-fix.patch
This patch was dropped because it was folded into mm-rmap-fix-cont-pte-pmd-size-hugetlb-issue-when-migration.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-rmap-fix-cont-pte-pmd-size-hugetlb-issue-when-migration-fix
fix nommu build
Cc: Baolin Wang <baolin.wang@linux.alibaba.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/hugetlb.h | 2 ++
1 file changed, 2 insertions(+)
--- a/include/linux/hugetlb.h~mm-rmap-fix-cont-pte-pmd-size-hugetlb-issue-when-migration-fix
+++ a/include/linux/hugetlb.h
@@ -1094,6 +1094,7 @@ static inline void set_huge_swap_pte_at(
{
}
+#ifdef CONFIG_MMU
static inline pte_t huge_ptep_clear_flush(struct vm_area_struct *vma,
unsigned long addr, pte_t *ptep)
{
@@ -1104,6 +1105,7 @@ static inline void set_huge_pte_at(struc
pte_t *ptep, pte_t pte)
{
}
+#endif
#endif /* CONFIG_HUGETLB_PAGE */
static inline spinlock_t *huge_pte_lock(struct hstate *h,
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
assoc_array-fix-bug_on-during-garbage-collect-fix.patch
mm-rmap-fix-cont-pte-pmd-size-hugetlb-issue-when-migration.patch
mm-start-tracking-vmas-with-maple-tree-fix.patch
damon-convert-__damon_va_three_regions-to-use-the-vma-iterator-fix.patch
mm-page_alloc-remotely-drain-per-cpu-lists-checkpatch-fixes.patch
tmpfs-fix-undefined-behaviour-in-shmem_reconfigure-fix.patch
linux-next-rejects.patch
linux-next-git-rejects.patch
mm-oom_killc-fix-vm_oom_kill_table-ifdeffery.patch
reply other threads:[~2022-05-13 22:34 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=20220513223441.C8369C34100@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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.