fs/dax: NIT fix comment regarding start/end vs range
Subsystems (2)
PATCH 1/1 fs/dax: NIT fix comment regarding start/end vs range
From: Ira Weiny <[email protected]>
Fixes ac46d4f3c432 ("mm/mmu_notifier: use structure for invalidate_range_start/end calls v2")
Signed-off-by Ira Weiny <[email protected]>
--- fs/dax.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/dax.c +1 -1
@@ -788,7 +788,7 @@ static void dax_entry_mkclean(struct address_space *mapping, pgoff_t index, address =pgoff_address (index, vma);/* -* Note because we provide start/end to follow_pte_pmd it will +* Note because we provide range to follow_pte_pmd it will * call mmu_notifier_invalidate_range_start() on our behalf * before taking any lock. */
Signature · 1 line
2.20.1
Jan Kara
reviewerQuoted 4 lines · On Thu 17-01-19 18:20:42, [email protected] wrote:
From: Ira Weiny <[email protected]>
Fixes ac46d4f3c432 ("mm/mmu_notifier: use structure for invalidate_range_start/end calls v2")Signed-off-by Ira Weiny <[email protected]>
Dan is merging DAX patches... Added to CC.
Honza
Quoted 20 lines
--- fs/dax.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)fs/dax.c +1
-1@@ -788,7 +788,7 @@ static void dax_entry_mkclean(struct address_space *mapping, pgoff_t index, address =pgoff_address (index, vma);/* -* Note because we provide start/end to follow_pte_pmd it will +* Note because we provide range to follow_pte_pmd it will * call mmu_notifier_invalidate_range_start() on our behalf * before taking any lock. */ Signature · 1 line
2.20.1
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR