* [PATCH] fs/dax: NIT fix comment regarding start/end vs range
@ 2019-01-17 23:20 ira.weiny
2019-01-23 11:56 ` Jan Kara
0 siblings, 1 reply; 2+ messages in thread
From: ira.weiny @ 2019-01-17 23:20 UTC (permalink / raw)
To: Alexander Viro, linux-fsdevel; +Cc: Ira Weiny
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(-)
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
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH] fs/dax: NIT fix comment regarding start/end vs range
2019-01-17 23:20 [PATCH] fs/dax: NIT fix comment regarding start/end vs range ira.weiny
@ 2019-01-23 11:56 ` Jan Kara
0 siblings, 0 replies; 2+ messages in thread
From: Jan Kara @ 2019-01-23 11:56 UTC (permalink / raw)
To: ira.weiny; +Cc: Alexander Viro, linux-fsdevel, Dan Williams
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
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-01-23 11:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-01-17 23:20 [PATCH] fs/dax: NIT fix comment regarding start/end vs range ira.weiny
2019-01-23 11:56 ` Jan Kara
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).