* fuse / work,mount coordination
@ 2019-09-06 17:07 Al Viro
2019-09-06 19:31 ` Miklos Szeredi
0 siblings, 1 reply; 3+ messages in thread
From: Al Viro @ 2019-09-06 17:07 UTC (permalink / raw)
To: Miklos Szeredi; +Cc: linux-fsdevel
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: fuse / work,mount coordination
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
0 siblings, 1 reply; 3+ messages in thread
From: Miklos Szeredi @ 2019-09-06 19:31 UTC (permalink / raw)
To: Al Viro; +Cc: linux-fsdevel
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.
Thanks,
Miklos
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: fuse / work,mount coordination
2019-09-06 19:31 ` Miklos Szeredi
@ 2019-09-06 20:24 ` Al Viro
0 siblings, 0 replies; 3+ messages in thread
From: Al Viro @ 2019-09-06 20:24 UTC (permalink / raw)
To: Miklos Szeredi; +Cc: linux-fsdevel
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-09-06 20:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).