[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190828142109.29012-1-hch@lst.de>
Date: Wed, 28 Aug 2019 16:21:09 +0200
From: Christoph Hellwig <hch@....de>
To: jgg@...lanox.com, akpm@...ux-foundation.org
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org, daniel@...ll.ch
Subject: [PATCH] mm: remove the __mmu_notifier_invalidate_range_start/end exports
Bo modular code uses these, which makes a lot of sense given the
wrappers around them are only called by core mm code.
Also remove the recently added __mmu_notifier_invalidate_range_start_map
export for which the same applies.
Signed-off-by: Christoph Hellwig <hch@....de>
---
mm/mmu_notifier.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/mm/mmu_notifier.c b/mm/mmu_notifier.c
index 690f1ea639d5..240f4e14d42e 100644
--- a/mm/mmu_notifier.c
+++ b/mm/mmu_notifier.c
@@ -25,7 +25,6 @@ DEFINE_STATIC_SRCU(srcu);
struct lockdep_map __mmu_notifier_invalidate_range_start_map = {
.name = "mmu_notifier_invalidate_range_start"
};
-EXPORT_SYMBOL_GPL(__mmu_notifier_invalidate_range_start_map);
#endif
/*
@@ -184,7 +183,6 @@ int __mmu_notifier_invalidate_range_start(struct mmu_notifier_range *range)
return ret;
}
-EXPORT_SYMBOL_GPL(__mmu_notifier_invalidate_range_start);
void __mmu_notifier_invalidate_range_end(struct mmu_notifier_range *range,
bool only_end)
@@ -218,7 +216,6 @@ void __mmu_notifier_invalidate_range_end(struct mmu_notifier_range *range,
srcu_read_unlock(&srcu, id);
lock_map_release(&__mmu_notifier_invalidate_range_start_map);
}
-EXPORT_SYMBOL_GPL(__mmu_notifier_invalidate_range_end);
void __mmu_notifier_invalidate_range(struct mm_struct *mm,
unsigned long start, unsigned long end)
--
2.20.1
Powered by blists - more mailing lists