mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-28 15:13:55 +08:00
939da10844
Ted has sent out a RFC about removing this feature. Eric and Jan confirmed that both RedHat and SUSE enable this feature in all their product. David also said that "As far as I know, it's enabled in all Android kernels that use ext4." So it seems OK for us. And what's more, as inline data depends its implementation on xattr, and to be frank, I don't run any test again inline data enabled while xattr disabled. So I think we should add inline data and remove this config option in the same release. [ The savings if you disable CONFIG_EXT4_FS_XATTR is only 27k, which isn't much in the grand scheme of things. Since no one seems to be testing this configuration except for some automated compile farms, on balance we are better removing this config option, and so that it is effectively always enabled. -- tytso ] Cc: David Brown <davidb@codeaurora.org> Cc: Eric Sandeen <sandeen@redhat.com> Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Tao Ma <boyu.mt@taobao.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
15 lines
480 B
Makefile
15 lines
480 B
Makefile
#
|
|
# Makefile for the linux ext4-filesystem routines.
|
|
#
|
|
|
|
obj-$(CONFIG_EXT4_FS) += ext4.o
|
|
|
|
ext4-y := balloc.o bitmap.o dir.o file.o fsync.o ialloc.o inode.o page-io.o \
|
|
ioctl.o namei.o super.o symlink.o hash.o resize.o extents.o \
|
|
ext4_jbd2.o migrate.o mballoc.o block_validity.o move_extent.o \
|
|
mmp.o indirect.o extents_status.o xattr.o xattr_user.o \
|
|
xattr_trusted.o inline.o
|
|
|
|
ext4-$(CONFIG_EXT4_FS_POSIX_ACL) += acl.o
|
|
ext4-$(CONFIG_EXT4_FS_SECURITY) += xattr_security.o
|