From: Al Viro <viro@zeniv.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: fuse / work,mount coordination
Date: Fri, 6 Sep 2019 21:24:59 +0100 [thread overview]
Message-ID: <20190906202459.GZ1131@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAJfpegvagSjXYg0zVKeJvJOBKJXBzVPZsBrovX6XM9qUPkB-ng@mail.gmail.com>
On Fri, Sep 06, 2019 at 09:31:39PM +0200, Miklos Szeredi wrote:
> On Fri, Sep 6, 2019 at 7:07 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > Could you switch your branch to pulling vfs.git#work.mount-base,
> > drop cherry-picked "vfs: Create fs_context-aware mount_bdev() replacement"
> > and use get_tree_bdev() instead of vfs_get_block_super()?
> >
> > I'd like to put #work.mount1 into -next instead of current
> > #work.mount, and doing that would obviously cause conflict with your
> > cherry-pick. #work.mount-base is the infrastructure part of that
> > series and it'll be in never-rebased mode.
>
> Done and pushed.
... and the same on my side.
prev parent reply other threads:[~2019-09-06 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 17:07 fuse / work,mount coordination Al Viro
2019-09-06 19:31 ` Miklos Szeredi
2019-09-06 20:24 ` Al Viro [this message]
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=20190906202459.GZ1131@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).