Message ID | 20200620071644.463185-5-hch@lst.de (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [01/10] tty/sysrq: emergency_thaw_all does not depend on CONFIG_BLOCK | expand |
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>
Looks good,
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
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.
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(-)