[PATCH] mm/huge_memory: use NULL instead of 0 for folio->private assignment.

[Zi Yan <ziy@xxxxxxxxxx>]

It makes sparse happy.

Reported-by: kernel test robot <lkp@xxxxxxxxx>
Closes: https://lore.kernel.org/oe-kbuild-all/202503131109.s7iuWfGq-lkp@xxxxxxxxx/
Signed-off-by: Zi Yan <ziy@xxxxxxxxxx>
---
 mm/huge_memory.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 14b1963898a7..e3ed8e9523f5 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -3369,7 +3369,7 @@ static void __split_folio_to_order(struct folio *folio, int old_order,
 		 */
 		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))
-- 
2.47.2



Best Regards,
Yan, Zi