From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org, peterx@redhat.com
Subject: [folded-merged] hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix.patch removed from -mm tree
Date: Tue, 04 May 2021 17:53:45 -0700 [thread overview]
Message-ID: <20210505005345.ZNBq3ntNv%akpm@linux-foundation.org> (raw)
The patch titled
Subject: hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix
has been removed from the -mm tree. Its filename was
hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix.patch
This patch was dropped because it was folded into hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share.patch
------------------------------------------------------
From: Peter Xu <peterx@redhat.com>
Subject: hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix
build fix
Link: https://lkml.kernel.org/r/20210304164653.GB397383@xz-x1
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/hugetlb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/hugetlb.c~hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share-fix
+++ a/mm/hugetlb.c
@@ -5450,7 +5450,7 @@ int huge_pmd_unshare(struct mm_struct *m
}
#define want_pmd_share() (1)
#else /* !CONFIG_ARCH_WANT_HUGE_PMD_SHARE */
-pte_t *huge_pmd_share(struct mm_struct *mm, struct vm_area_struct vma,
+pte_t *huge_pmd_share(struct mm_struct *mm, struct vm_area_struct *vma,
unsigned long addr, pud_t *pud)
{
return NULL;
_
Patches currently in -mm which might be from peterx@redhat.com are
hugetlb-pass-vma-into-huge_pte_alloc-and-huge_pmd_share.patch
hugetlb-userfaultfd-forbid-huge-pmd-sharing-when-uffd-enabled.patch
hugetlb-userfaultfd-forbid-huge-pmd-sharing-when-uffd-enabled-fix.patch
mm-hugetlb-move-flush_hugetlb_tlb_range-into-hugetlbh.patch
hugetlb-userfaultfd-unshare-all-pmds-for-hugetlbfs-when-register-wp.patch
userfaultfd-add-minor-fault-registration-mode-fix.patch
mm-hugetlb-fix-f_seal_future_write.patch
mm-hugetlb-fix-cow-where-page-writtable-in-child.patch
reply other threads:[~2021-05-05 0:53 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=20210505005345.ZNBq3ntNv%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=peterx@redhat.com \
/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.