From 0cefc36b32b3a9ee9da9bd055810bf331e4243dd Mon Sep 17 00:00:00 2001 From: Ira Weiny Date: Thu, 17 Jan 2019 18:20:42 -0500 Subject: fs/dax: NIT fix comment regarding start/end vs range Fixes: ac46d4f3c432 ("mm/mmu_notifier: use structure for invalidate_range_start/end calls v2") Signed-off-by: Ira Weiny Signed-off-by: Dan Williams --- fs/dax.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'fs/dax.c') diff --git a/fs/dax.c b/fs/dax.c index 7865d9080085..c55afa4261d1 100644 --- a/fs/dax.c +++ b/fs/dax.c @@ -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. */ -- cgit