From: Baokun Li <libaokun@huaweicloud.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Gao Xiang <xiang@kernel.org>,
Christian Brauner <brauner@kernel.org>,
Gao Xiang <hsiangkao@linux.alibaba.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
libaokun@huaweicloud.com
Subject: Re: linux-next: manual merge of the vfs-brauner tree with the erofs-fixes tree
Date: Wed, 24 Apr 2024 09:26:30 +0800 [thread overview]
Message-ID: <b7332fb7-4c49-3af2-7095-e728a6af8ff7@huaweicloud.com> (raw)
In-Reply-To: <20240424102445.53ba5ba2@canb.auug.org.au>
Hi Stephen,
On 2024/4/24 8:24, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the vfs-brauner tree got a conflict in:
>
> fs/erofs/super.c
>
> between commits:
>
> ab1bbc1735ff ("erofs: get rid of erofs_fs_context")
> 569a48fed355 ("erofs: reliably distinguish block based and fscache mode")
>
> from the erofs-fixes tree and commit:
>
> e4f586a41748 ("erofs: reliably distinguish block based and fscache mode")
>
> from the vfs-brauner tree.
>
> I fixed it up (I think - I used the former version) 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.
>
Christian previously mentioned that the fix from the vfs-brauner tree
was an accident:
"An an accident on my part as I left it in the vfs.fixes branch."
So the two commits from the erofs-fixes tree are the final fixes.
I'm very sorry for any inconvenience caused.
Thanks,
Baokun
next prev parent reply other threads:[~2024-04-24 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 0:24 Stephen Rothwell
2024-04-24 1:26 ` Baokun Li [this message]
2024-04-24 2:13 ` Gao Xiang
2024-04-24 12:51 ` Christian Brauner
2024-04-25 1:55 ` 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=b7332fb7-4c49-3af2-7095-e728a6af8ff7@huaweicloud.com \
--to=libaokun@huaweicloud.com \
--cc=brauner@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xiang@kernel.org \
/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
all inboxes | Powered by JetHome®