Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935190Ab3IDPtZ (ORCPT ); Wed, 4 Sep 2013 11:49:25 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59228 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934808Ab3IDPtX (ORCPT ); Wed, 4 Sep 2013 11:49:23 -0400 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: References: To: Sage Weil Cc: dhowells@redhat.com, Milosz Tanski , 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 Message-ID: <17341.1378309753@warthog.procyon.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 906 Lines: 22 Sage Weil 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/