From: Christoph Hellwig <hch@lst.de>
Date: Sat, 20 Jun 2020 09:16:38 +0200
Subject: [PATCH] fs: remove the HAVE_UNLOCKED_IOCTL and HAVE_COMPAT_IOCTL
Git-commit: 4e24566a134ea167441a1ffa3d439a27cf400880
Patch-mainline: v5.9-rc1
References: bsc#1175995,jsc#SLE-15608
 defines

These are not defined anywhere, and contrary to the comments we really
do not care about out of tree code at all.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Acked-by: Hannes Reinecke <hare@suse.com>
---
 include/linux/fs.h | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/include/linux/fs.h b/include/linux/fs.h
index 0d282c853691..224edcc5b56e 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1774,12 +1774,6 @@ struct dir_context {
 	loff_t pos;
 };
 
-/* These macros are for out of kernel modules to test that
- * the kernel supports the unlocked_ioctl and compat_ioctl
- * fields in struct file_operations. */
-#define HAVE_COMPAT_IOCTL 1
-#define HAVE_UNLOCKED_IOCTL 1
-
 /*
  * These flags let !MMU mmap() govern direct device mapping vs immediate
  * copying more easily for MAP_PRIVATE, especially for ROM filesystems.
-- 
2.16.4