From: David Howells <dhowells@redhat.com>
To: Sage Weil <sage@inktank.com>
Cc: dhowells@redhat.com, Milosz Tanski <milosz@adfin.com>,
ceph-devel@vger.kernel.org, zheng.z.yan@intel.com,
linux-cachefs@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCHv4 0/5] ceph: persistent caching with fscache
Date: Wed, 04 Sep 2013 16:49:13 +0100 [thread overview]
Message-ID: <17341.1378309753@warthog.procyon.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1308212203320.1479@cobra.newdream.net>
Sage Weil <sage@inktank.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.
David
next prev parent reply other threads:[~2013-09-04 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 21:26 [PATCHv4 0/5] ceph: persistent caching with fscache Milosz Tanski
2013-08-22 5:05 ` Sage Weil
2013-08-22 12:58 ` Milosz Tanski
2013-09-04 15:49 ` David Howells [this message]
2013-09-04 15:54 ` Sage Weil
2013-09-04 16:25 ` Sage Weil
2013-09-05 12:34 ` David Howells
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=17341.1378309753@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=milosz@adfin.com \
--cc=sage@inktank.com \
--cc=zheng.z.yan@intel.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).