From f0ade90a8aa1ea523eb366d1d1e8bd3463d9cf8a Mon Sep 17 00:00:00 2001 From: Christoph Hellwig Date: Wed, 28 Aug 2019 16:21:09 +0200 Subject: [PATCH] mm/mmu_notifiers: remove the __mmu_notifier_invalidate_range_start/end exports No modular code uses these, which makes a lot of sense given the wrappers around them are only called by core mm code. Link: https://lore.kernel.org/r/20190828142109.29012-1-hch@lst.de Signed-off-by: Christoph Hellwig Reviewed-by: Jason Gunthorpe Signed-off-by: Jason Gunthorpe --- mm/mmu_notifier.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/mm/mmu_notifier.c b/mm/mmu_notifier.c index 3ebdc748b168..9e2125ae10a5 100644 --- a/mm/mmu_notifier.c +++ b/mm/mmu_notifier.c @@ -177,7 +177,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) @@ -209,7 +208,6 @@ void __mmu_notifier_invalidate_range_end(struct mmu_notifier_range *range, } srcu_read_unlock(&srcu, id); } -EXPORT_SYMBOL_GPL(__mmu_notifier_invalidate_range_end); void __mmu_notifier_invalidate_range(struct mm_struct *mm, unsigned long start, unsigned long end) @@ -224,7 +222,6 @@ void __mmu_notifier_invalidate_range(struct mm_struct *mm, } srcu_read_unlock(&srcu, id); } -EXPORT_SYMBOL_GPL(__mmu_notifier_invalidate_range); /* * Same as mmu_notifier_register but here the caller must hold the