Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758883AbZFSXYw (ORCPT ); Fri, 19 Jun 2009 19:24:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756031AbZFSXYj (ORCPT ); Fri, 19 Jun 2009 19:24:39 -0400 Received: from kroah.org ([198.145.64.141]:34334 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756103AbZFSXYi (ORCPT ); Fri, 19 Jun 2009 19:24:38 -0400 Date: Fri, 19 Jun 2009 16:19:55 -0700 From: Greg KH To: Sage Weil Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH 00/21] ceph: Ceph distributed file system client v0.9 Message-ID: <20090619231955.GE19582@kroah.com> References: <1245450702-31343-1-git-send-email-sage@newdream.net> <20090619224524.GB27322@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1703 Lines: 40 On Fri, Jun 19, 2009 at 04:12:51PM -0700, Sage Weil wrote: > On Fri, 19 Jun 2009, Greg KH wrote: > > On Fri, Jun 19, 2009 at 03:31:21PM -0700, Sage Weil wrote: > > > This is a patch series for v0.9 of the Ceph distributed file system > > > client (against v2.6.30). > > > > Oh, one other question, why put this in staging? What is keeping it > > being accepted into fs/ like normal? > > I would obviously prefer that route, but my assumption has been that the > code needs some review and a core developer to sign off on it before that > can happen. I've posted the patchset a few times now, and haven't gotten > much response. If there is something else I can or should be doing to > push this upstream, I'm all ears... Have you posted it on the linux filesystems list? I haven't noticed it there, but I might have missed it. > The code certainly isn't ready for production, but the client code at > least has seen relatively few changes recently. Our internal testing is > ramping up in scale and so far we're primarily working out problems with > the server side daemons. > > I'm not quite sure what the criteria for mainline inclusion is, as it > seems to vary from file system to file system, but from my perspective > any move upstream can only help. Review from the above mentioned list should be all that is needed. If after that, you still want it in drivers/staging/, please feel free to send it to me. good luck, greg k-h -- 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/