Skip to contentSkip to conversation

thp: update split_huge_page_pmd() commnet

PATCH New Kefeng Wang 1 participant 1 message Jul 31, 2019

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 thp: update split_huge_page_pmd() commnet

According to 78ddc5347341 ("thp: rename split_huge_page_pmd() to split_huge_pmd()"), update releated comment.

---
 arch/powerpc/mm/book3s64/hash_utils.c | 2 +-
 include/asm-generic/pgtable.h         | 5 ++---
 2 files changed, 3 insertions(+), 4 deletions(-)
arch/powerpc/mm/book3s64/hash_utils.c +1 -1
index b8ad14bb1170..cebd1acaddac 100644
@@ -1705,7 +1705,7 @@ void flush_hash_hugepage(unsigned long vsid, unsigned long addr,
 	/*
 	 * IF we try to do a HUGE PTE update after a withdraw is done.
 	 * we will find the below NULL. This happens when we do
-	 * split_huge_page_pmd
+	 * split_huge_pmd
 	 */
 	if (!hpte_slot_array)
 		return;
include/asm-generic/pgtable.h +2 -3
index 75d9d68a6de7..0e25f556a99b 100644
@@ -1002,9 +1002,8 @@ static inline int pmd_none_or_trans_huge_or_clear_bad(pmd_t *pmd)
  * need this). If THP is not enabled, the pmd can't go away under the
  * code even if MADV_DONTNEED runs, but if THP is enabled we need to
  * run a pmd_trans_unstable before walking the ptes after
- * split_huge_page_pmd returns (because it may have run when the pmd
- * become null, but then a page fault can map in a THP and not a
- * regular page).
+ * split_huge_pmd returns (because it may have run when the pmd become
+ * null, but then a page fault can map in a THP and not a regular page).
  */
 static inline int pmd_trans_unstable(pmd_t *pmd)
 {
Signature · 1 line
2.20.1