[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20240906082704.2a7f5a8d@canb.auug.org.au>
Date: Fri, 6 Sep 2024 08:27:04 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>
Cc: Jeff Layton <jlayton@...nel.org>, Josef Bacik <josef@...icpanda.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the vfs-brauner tree with the ext3 tree
Hi all,
Today's linux-next merge of the vfs-brauner tree got a conflict in:
fs/ext4/super.c
between commit:
fab2eb0fd1b8 ("ext4: enable pre-content events")
from the ext3 tree and commit:
729f35ab8b0a ("ext4: switch to multigrain timestamps")
from the vfs-brauner tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc fs/ext4/super.c
index a1a84100b230,a125d9435b8a..000000000000
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@@ -7329,7 -7298,7 +7329,8 @@@ static struct file_system_type ext4_fs_
.init_fs_context = ext4_init_fs_context,
.parameters = ext4_param_specs,
.kill_sb = ext4_kill_sb,
- .fs_flags = FS_REQUIRES_DEV | FS_ALLOW_IDMAP | FS_ALLOW_HSM,
- .fs_flags = FS_REQUIRES_DEV | FS_ALLOW_IDMAP | FS_MGTIME,
++ .fs_flags = FS_REQUIRES_DEV | FS_ALLOW_IDMAP |
++ FS_ALLOW_HSM | FS_MGTIME,
};
MODULE_ALIAS_FS("ext4");
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists