The patch titled
Subject: mm/hugetlb: __unmap_hugepage_range() can be static
has been added to the -mm tree. Its filename is
mm-hugetlb-__unmap_hugepage_range-can-be-static.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/mm-hugetlb-__unmap_hugepage_range-can-be-static.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/mm-hugetlb-__unmap_hugepage_range-can-be-static.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: kernel test robot <lkp@xxxxxxxxx>
Subject: mm/hugetlb: __unmap_hugepage_range() can be static
mm/hugetlb.c:4334:6: warning: symbol '__unmap_hugepage_range' was not declared. Should it be static?
Link: https://lkml.kernel.org/r/20210715170524.GA48547@78ef4ef0cd6c
Signed-off-by: kernel test robot <lkp@xxxxxxxxx>
Reported-by: kernel test robot <lkp@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/hugetlb.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- a/mm/hugetlb.c~mm-hugetlb-__unmap_hugepage_range-can-be-static
+++ a/mm/hugetlb.c
@@ -4402,9 +4402,9 @@ again:
return ret;
}
-void __unmap_hugepage_range(struct mmu_gather *tlb, struct vm_area_struct *vma,
- unsigned long start, unsigned long end,
- struct page *ref_page)
+static void __unmap_hugepage_range(struct mmu_gather *tlb, struct vm_area_struct *vma,
+ unsigned long start, unsigned long end,
+ struct page *ref_page)
{
struct mm_struct *mm = vma->vm_mm;
unsigned long address;
_
Patches currently in -mm which might be from lkp@xxxxxxxxx are
lib-fix-bugoncocci-warnings.patch
mm-hugetlb-__unmap_hugepage_range-can-be-static.patch
