From: Al Viro <viro@zeniv.linux.org.uk>
To: Gao Xiang <hsiangkao@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Gao Xiang <xiang@kernel.org>,
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: Re: linux-next: manual merge of the vfs tree with the erofs tree
Date: Fri, 29 May 2020 15:36:13 +0100 [thread overview]
Message-ID: <20200529143613.GE23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200529034007.GA12648@xiangao.remote.csb>
On Fri, May 29, 2020 at 11:40:07AM +0800, Gao Xiang wrote:
> I'm fine with that, although I think it's mainly with vfs changes
> so could be better though with vfs tree. I will add this patch
> tomorrow anyway... Thanks for reminder!
FWIW, my reasoning here is
* erofs tree exists and
* the patch is erofs-specific, affects nothing outside and
has no dependencies with anything currently done in VFS or in other
filesystems and
* it does have (trivial) conflicts with the stuff in
erofs tree
So putting it into erofs tree would seem to be an obvious approach -
minimizes the amount of cross-tree dependencies and headache for
everyone involved...
I'm dropping it from #work.misc and #for-next now.
next prev parent reply other threads:[~2020-05-29 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 1:45 linux-next: manual merge of the vfs tree with the erofs tree Stephen Rothwell
2020-05-29 1:51 ` Al Viro
2020-05-29 3:40 ` Gao Xiang
2020-05-29 14:36 ` Al Viro [this message]
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=20200529143613.GE23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=cgxu519@mykernel.net \
--cc=hsiangkao@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).