[Virtio-fs] [PATCH 2/2] fuse: make FUSE_REMOVEMAPPING_MAX_ENTRY private

[Stefan Hajnoczi]

FUSE_REMOVEMAPPING_MAX_ENTRY is only used by fs/fuse/file.c and is not
part of the FUSE protocol.  Do not expose it in the uapi header file.

Signed-off-by: Stefan Hajnoczi <stefanha at redhat.com>
---
 include/uapi/linux/fuse.h | 3 ---
 fs/fuse/file.c            | 3 +++
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/include/uapi/linux/fuse.h b/include/uapi/linux/fuse.h
index 8c36aadb6294..0f4b69b9c751 100644
--- a/include/uapi/linux/fuse.h
+++ b/include/uapi/linux/fuse.h
@@ -853,7 +853,4 @@ struct fuse_removemapping_one {
         uint64_t	len;
 };
 
-#define FUSE_REMOVEMAPPING_MAX_ENTRY   \
-		(PAGE_SIZE / sizeof(struct fuse_removemapping_one))
-
 #endif /* _LINUX_FUSE_H */
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index fc40e0f44578..1e890a8491ae 100644
--- a/fs/fuse/file.c
+++ b/fs/fuse/file.c
@@ -22,6 +22,9 @@
 #include <linux/iomap.h>
 #include <linux/interval_tree_generic.h>
 
+#define FUSE_REMOVEMAPPING_MAX_ENTRY   \
+		(PAGE_SIZE / sizeof(struct fuse_removemapping_one))
+
 INTERVAL_TREE_DEFINE(struct fuse_dax_mapping, rb, __u64, __subtree_last,
                      START, LAST, static inline, fuse_dax_interval_tree);
 
-- 
2.21.0