From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,ziy@nvidia.com,vbabka@kernel.org,pfalcato@suse.de,ljs@kernel.org,liam@infradead.org,jannh@google.com,david@kernel.org,wangkefeng.wang@huawei.com,akpm@linux-foundation.org
Subject: [folded-merged] mm-mincore-remove-special-handling-for-vm_pfnmap-fix.patch removed from -mm tree
Date: Tue, 04 Aug 2026 18:23:16 -0700 [thread overview]
Message-ID: <20260805012317.398D61F000E9@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: mincore: fixup for remove special handling for VM_PFNMAP
has been removed from the -mm tree. Its filename was
mm-mincore-remove-special-handling-for-vm_pfnmap-fix.patch
This patch was dropped because it was folded into mm-mincore-remove-special-handling-for-vm_pfnmap.patch
------------------------------------------------------
From: Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: mm: mincore: fixup for remove special handling for VM_PFNMAP
Date: Mon, 20 Jul 2026 20:41:51 +0800
Address David's comments
- rename mincore_pud_range to mincore_pud_entry
- change int nr to const unsigned long
- remove a local vec variable
Link: https://lore.kernel.org/20260720124151.1483820-1-wangkefeng.wang@huawei.com
Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: David Hildenbrand (Arm) <david@kernel.org>
Cc: Jann Horn <jannh@google.com>
Cc: Liam R. Howlett <liam@infradead.org>
Cc: Lorenzo Stoakes <ljs@kernel.org>
Cc: Pedro Falcato <pfalcato@suse.de>
Cc: Vlastimil Babka <vbabka@kernel.org>
Cc: Zi Yan <ziy@nvidia.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/mincore.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
--- a/mm/mincore.c~mm-mincore-remove-special-handling-for-vm_pfnmap-fix
+++ a/mm/mincore.c
@@ -160,16 +160,15 @@ static int mincore_unmapped_range(unsign
return 0;
}
-static int mincore_pud_range(pud_t *pudp, unsigned long addr, unsigned long end,
+static int mincore_pud_entry(pud_t *pudp, unsigned long addr, unsigned long end,
struct mm_walk *walk)
{
if (pud_is_huge(pudp_get(pudp))) {
- int nr = (end - addr) >> PAGE_SHIFT;
- unsigned char *vec = walk->private;
+ const unsigned long nr = (end - addr) >> PAGE_SHIFT;
- memset(vec, 1, nr);
- walk->action = ACTION_CONTINUE;
+ memset(walk->private, 1, nr);
walk->private += nr;
+ walk->action = ACTION_CONTINUE;
}
return 0;
@@ -247,7 +246,7 @@ static inline bool can_do_mincore(struct
}
static const struct mm_walk_ops mincore_walk_ops = {
- .pud_entry = mincore_pud_range,
+ .pud_entry = mincore_pud_entry,
.pmd_entry = mincore_pte_range,
.pte_hole = mincore_unmapped_range,
.hugetlb_entry = mincore_hugetlb,
_
Patches currently in -mm which might be from wangkefeng.wang@huawei.com are
mm-introduce-pud_is_huge-helper.patch
mm-mincore-remove-special-handling-for-vm_pfnmap.patch
mm-mincore-replace-__get_free_page-with-kmalloc.patch
mm-mincore-remove-xa_is_value-in-mincore_swap.patch
mm-mincore-improve-mincore_hugetlb.patch
mm-mincore-improve-mincore_hugetlb-fix.patch
mm-mincore-refactor-mincore_page.patch
reply other threads:[~2026-08-05 1:23 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=20260805012317.398D61F000E9@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=ljs@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=pfalcato@suse.de \
--cc=vbabka@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=ziy@nvidia.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.