diff mbox series

fs/dax: NIT fix comment regarding start/end vs range

Message ID 20190117232042.10964-1-ira.weiny@intel.com (mailing list archive)
State New, archived
Headers show
Series fs/dax: NIT fix comment regarding start/end vs range | expand

Commit Message

Ira Weiny Jan. 17, 2019, 11:20 p.m. UTC
From: Ira Weiny <ira.weiny@intel.com>

Fixes: ac46d4f3c432 ("mm/mmu_notifier: use structure for invalidate_range_start/end calls v2")
Signed-off-by: Ira Weiny <ira.weiny@intel.com>

---
 fs/dax.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

Jan Kara Jan. 23, 2019, 11:56 a.m. UTC | #1
On Thu 17-01-19 18:20:42, ira.weiny@intel.com wrote:
> From: Ira Weiny <ira.weiny@intel.com>
> 
> Fixes: ac46d4f3c432 ("mm/mmu_notifier: use structure for invalidate_range_start/end calls v2")
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>

Dan is merging DAX patches... Added to CC.

								Honza

> ---
>  fs/dax.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/dax.c b/fs/dax.c
> index 6959837cc465..a5898fa866f9 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.
>  		 */
> -- 
> 2.20.1
>
diff mbox series

Patch

diff --git a/fs/dax.c b/fs/dax.c
index 6959837cc465..a5898fa866f9 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.
 		 */