[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1309040851080.27503@cobra.newdream.net>
Date: Wed, 4 Sep 2013 08:54:34 -0700 (PDT)
From: Sage Weil <sage@...tank.com>
To: David Howells <dhowells@...hat.com>
cc: Milosz Tanski <milosz@...in.com>, ceph-devel@...r.kernel.org,
zheng.z.yan@...el.com, linux-cachefs@...hat.com,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nfs@...r.kernel.org
Subject: Re: [PATCHv4 0/5] ceph: persistent caching with fscache
Hi David!
On Wed, 4 Sep 2013, David Howells wrote:
> Sage Weil <sage@...tank.com> wrote:
>
> > David, are the fscache patches here ready for the next merge window? Do
> > you have a preference for whose tree they go through?
>
> There's only one problem - patch 1 needs to come _after_ patch 2 to avoid
> breaking git bisect. Plus these patches 2 and 4 extend the fscache API
> without adjusting the documentation - but that can be added later.
>
> And I think Milosz deserves a beer (or other poison of his choice;-) for
> finding a longstanding irritating bug.
>
> I think AFS, CIFS, NFS and 9P all need patching too, but I can attend to that.
>
> Should I take the patches through my tree? Then I can make the adjustments.
Sure. Do you want the Ceph patches as well, or just the fscache bits?
I'll repost the latest version, as it's gotten several fixes squashed in.
Thanks!
sage
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists