diff options
| author | David Hildenbrand <[email protected]> | 2024-07-31 16:20:00 +0200 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2024-09-01 20:25:57 -0700 |
| commit | 94ccd21e9a5f41585bd16cc84dab2afa6cc21149 (patch) | |
| tree | d3543805384a4c1c3accd0500da924fb43e667d7 /tools/perf/scripts/python/exported-sql-viewer.py | |
| parent | f732e242841a9775b71744fa6b9bf6f25215b11f (diff) | |
mm/hugetlb: remove hugetlb_follow_page_mask() leftover
We removed hugetlb_follow_page_mask() in commit 9cb28da54643 ("mm/gup:
handle hugetlb in the generic follow_page_mask code") but forgot to
cleanup some leftovers.
While at it, simplify the hugetlb comment, it's overly detailed and rather
confusing. Stating that we may end up in there during coredumping is
sufficient to explain the PF_DUMPCORE usage.
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: David Hildenbrand <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Cc: Muchun Song <[email protected]>
Cc: Alexander Viro <[email protected]>
Cc: Christian Brauner <[email protected]>
Cc: Jan Kara <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions