The quilt patch titled
Subject: mm/huge_memory: use NULL instead of 0 for folio->private assignment
has been removed from the -mm tree. Its filename was
mm-huge_memory-add-two-new-not-yet-used-functions-for-folio_split-fix-2.patch
This patch was dropped because it was folded into mm-huge_memory-add-two-new-not-yet-used-functions-for-folio_split.patch
------------------------------------------------------
From: Zi Yan <ziy@xxxxxxxxxx>
Subject: mm/huge_memory: use NULL instead of 0 for folio->private assignment
Date: Thu, 13 Mar 2025 10:04:20 -0400
It makes sparse happy.
Link: https://lkml.kernel.org/r/1E11B9DD-3A87-4C9C-8FB4-E1324FB6A21A@xxxxxxxxxx
Signed-off-by: Zi Yan <ziy@xxxxxxxxxx>
Reported-by: kernel test robot <lkp@xxxxxxxxx>
Closes: https://lore.kernel.org/oe-kbuild-all/202503131109.s7iuWfGq-lkp@xxxxxxxxx/
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/huge_memory.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/huge_memory.c~mm-huge_memory-add-two-new-not-yet-used-functions-for-folio_split-fix-2
+++ a/mm/huge_memory.c
@@ -3584,7 +3584,7 @@ static void __split_folio_to_order(struc
*/
if (unlikely(new_folio->private)) {
VM_WARN_ON_ONCE_PAGE(true, new_head);
- new_folio->private = 0;
+ new_folio->private = NULL;
}
if (folio_test_swapcache(folio))
_
Patches currently in -mm which might be from ziy@xxxxxxxxxx are
xarray-add-xas_try_split-to-split-a-multi-index-entry.patch
mm-huge_memory-add-two-new-not-yet-used-functions-for-folio_split.patch
mm-huge_memory-move-folio-split-common-code-to-__folio_split.patch
mm-huge_memory-add-buddy-allocator-like-non-uniform-folio_split.patch
mm-huge_memory-remove-the-old-unused-__split_huge_page.patch
mm-huge_memory-add-folio_split-to-debugfs-testing-interface.patch
mm-truncate-use-folio_split-in-truncate-operation.patch
selftests-mm-add-tests-for-folio_split-buddy-allocator-like-split.patch
mm-filemap-use-xas_try_split-in-__filemap_add_folio.patch
mm-shmem-use-xas_try_split-in-shmem_split_large_entry.patch
