From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Al Viro <viro@ZenIV.linux.org.uk>, Gao Xiang <xiang@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chengguang Xu <cgxu519@mykernel.net>,
Chao Yu <yuchao0@huawei.com>
Subject: linux-next: manual merge of the vfs tree with the erofs tree
Date: Fri, 29 May 2020 11:45:01 +1000 [thread overview]
Message-ID: <20200529114501.3e2ecc14@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
fs/erofs/super.c
between commit:
e7cda1ee94f4 ("erofs: code cleanup by removing ifdef macro surrounding")
from the erofs tree and commit:
91a7c5e1d30e ("erofs: convert to use the new mount fs_context api")
from the vfs 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/erofs/super.c
index 8e46d204a0c2,2c0bad903fa6..000000000000
--- a/fs/erofs/super.c
+++ b/fs/erofs/super.c
@@@ -408,16 -365,12 +365,9 @@@ static int erofs_fc_fill_super(struct s
sb->s_time_gran = 1;
sb->s_op = &erofs_sops;
-
-#ifdef CONFIG_EROFS_FS_XATTR
sb->s_xattr = erofs_xattr_handlers;
-#endif
- /* set erofs default mount options */
- erofs_default_options(sbi);
-
- err = erofs_parse_options(sb, data);
- if (err)
- return err;
-
- if (test_opt(sbi, POSIX_ACL))
+ if (test_opt(ctx, POSIX_ACL))
sb->s_flags |= SB_POSIXACL;
else
sb->s_flags &= ~SB_POSIXACL;
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-05-29 1:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 1:45 Stephen Rothwell [this message]
2020-05-29 1:51 ` linux-next: manual merge of the vfs tree with the erofs tree Al Viro
2020-05-29 3:40 ` Gao Xiang
2020-05-29 14:36 ` Al Viro
2020-05-29 14:50 ` Gao Xiang
-- strict thread matches above, loose matches on Subject: below --
2022-11-27 22:13 Stephen Rothwell
2022-11-28 2:12 ` Jingbo Xu
2022-12-04 22:24 Stephen Rothwell
2022-12-05 3:13 ` Gao Xiang
2022-12-05 4:11 ` Stephen Rothwell
2022-12-05 4:43 ` Gao Xiang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200529114501.3e2ecc14@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cgxu519@mykernel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=xiang@kernel.org \
--cc=yuchao0@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).