It seems that you are more active than dorimanx/exfat-nofuse, so I create my PR here :)
In torvalds/linux@e462ec50cb a new set of superblock flags was added to replace the original MS* ones, and in torvalds/linux@e262e32d6b the MS* flags are suppressed unless uapi/linux/mount.h is included. As is suggested, we should use the new API now.
I compiled it with Linux Kernel 5.0-rc1, and the build was successful. Though I haven't run the kernel yet, I think it just works.
The following changes since commit f93a47e6414d567a1e7f6ab7f34b015b20f9a050:
Fix for 4.20 (2018-12-31 16:50:33 +0000)
are available in the Git repository at:
https://github.com/lmy441900/exfat-nofuse
for you to fetch changes up to 8b59e1f338fdd87f1d5a9db2a119a3745bb467d5:
exfat_{core,super}.c: fix build on 5.0-rc1, MS_* -> SB_* (2019-01-10 23:13:35 +0800)
----------------------------------------------------------------
Junde Yhi (1):
exfat_{core,super}.c: fix build on 5.0-rc1, MS_* -> SB_*
exfat_core.c | 6 +++++-
exfat_core.h | 6 ++++++
exfat_super.c | 11 ++++++++++-
3 files changed, 21 insertions(+), 2 deletions(-)
It seems that you are more active than dorimanx/exfat-nofuse, so I create my PR here :)
In torvalds/linux@e462ec50cb a new set of superblock flags was added to replace the original MS* ones, and in torvalds/linux@e262e32d6b the MS* flags are suppressed unless uapi/linux/mount.h is included. As is suggested, we should use the new API now.
I compiled it with Linux Kernel 5.0-rc1, and the build was successful. Though I haven't run the kernel yet, I think it just works.