diff options
author | Ira Weiny <ira.weiny@intel.com> | 2019-01-17 18:20:42 -0500 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2019-02-12 20:24:15 -0800 |
commit | 0cefc36b32b3a9ee9da9bd055810bf331e4243dd (patch) | |
tree | 8996fbf80bc0a48e7180472919a713e464db4476 /fs/dax.c | |
parent | c9aed74e6a2762c32e9b84fcd5e1b9bc451ffdfd (diff) |
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 <ira.weiny@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'fs/dax.c')
-rw-r--r-- | fs/dax.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -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. */ |