[04/10] fs: remove the HAVE_UNLOCKED_IOCTL and HAVE_COMPAT_IOCTL defines
diff mbox series

Message ID 20200620071644.463185-5-hch@lst.de
State New
Headers show
Series
  • [01/10] tty/sysrq: emergency_thaw_all does not depend on CONFIG_BLOCK
Related show

Commit Message

Christoph Hellwig June 20, 2020, 7:16 a.m. UTC
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>
---
 include/linux/fs.h | 6 ------
 1 file changed, 6 deletions(-)

Comments

Bart Van Assche June 21, 2020, 2:56 a.m. UTC | #1
On 2020-06-20 00:16, Christoph Hellwig wrote:
> These are not defined anywhere, and contrary to the comments we really
> do not care about out of tree code at all.

Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Johannes Thumshirn June 22, 2020, 9:13 a.m. UTC | #2
Looks good,
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>

Patch
diff mbox series

diff --git a/include/linux/fs.h b/include/linux/fs.h
index 0d282c853691a3..224edcc5b56e62 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.