[PATCH v2 2/5] mmu_notifiers: Fixup comment in mmu_interval_read_begin()

[Alistair Popple]

The comment in mmu_interval_read_begin() refers to a function that
doesn't exist and uses the wrong call-back name. The op for mmu
interval notifiers is mmu_interval_notifier_ops->invalidate() so fix
the comment up to reflect that.

Signed-off-by: Alistair Popple <apop...@nvidia.com>
---
 mm/mmu_notifier.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/mm/mmu_notifier.c b/mm/mmu_notifier.c
index 50c0dde..b7ad155 100644
--- a/mm/mmu_notifier.c
+++ b/mm/mmu_notifier.c
@@ -199,7 +199,7 @@ mmu_interval_read_begin(struct mmu_interval_notifier 
*interval_sub)
         * invalidate_start/end and is colliding.
         *
         * The locking looks broadly like this:
-        *   mn_tree_invalidate_start():          mmu_interval_read_begin():
+        *   mn_itree_inv_start():                 mmu_interval_read_begin():
         *                                         spin_lock
         *                                          seq = 
READ_ONCE(interval_sub->invalidate_seq);
         *                                          seq == subs->invalidate_seq
@@ -207,7 +207,7 @@ mmu_interval_read_begin(struct mmu_interval_notifier 
*interval_sub)
         *    spin_lock
         *     seq = ++subscriptions->invalidate_seq
         *    spin_unlock
-        *     op->invalidate_range():
+        *     op->invalidate():
         *       user_lock
         *        mmu_interval_set_seq()
         *         interval_sub->invalidate_seq = seq
-- 
git-series 0.9.1