[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOi1vP_sEj7i8YbbwJibbSG=BCVp4E9BAo=JF0aC79xBNC8wcA@mail.gmail.com>
Date: Sat, 19 Mar 2022 13:46:25 +0100
From: Ilya Dryomov <idryomov@...il.com>
To: David Howells <dhowells@...hat.com>
Cc: Jeff Layton <jlayton@...nel.org>, Xiubo Li <xiubli@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ceph Development <ceph-devel@...r.kernel.org>,
linux-cachefs@...hat.com, linux-afs@...ts.infradead.org,
linux-nfs@...r.kernel.org, linux-cifs@...r.kernel.org,
v9fs-developer@...ts.sourceforge.net,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Coordinating netfslib pull request with the ceph pull request
On Sat, Mar 19, 2022 at 1:02 AM David Howells <dhowells@...hat.com> wrote:
>
> Hi Ilya,
>
> Since my fscache-next branch[1] is dependent on patches in the ceph/master
> branch, I think I need to coordinate my netfslib pull request with your ceph
> pull request for the upcoming merge window.
>
> David
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-next
>
Hi David,
Given how your branch is structured, it sounds like the easiest would
be for you to send the netfslib pull request after I send the ceph pull
request. Or do you have some tighter coordination in mind?
Thanks,
Ilya
Powered by blists - more mailing lists