From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: Mainlining Lustre client Date: Sat, 27 Apr 2013 08:56:32 -0700 Message-ID: <20130427155632.GF19487@tassilo.jf.intel.com> References: <1882637210201641A747464075FFC649025BEEEA@MX101CL02.corp.emc.com> <20130427132144.GC32432@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Peng, Tao" , Al Viro , "linux-fsdevel@vger.kernel.org" , Christoph Hellwig , Andreas Dilger , Matthew Wilcox , Theodore Ts'o , "Myklebust, Trond" , "faibish, sorin" , "Tang, Haiying" To: Greg Kroah-Hartman Return-path: Received: from mga01.intel.com ([192.55.52.88]:45506 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755081Ab3D0P4e (ORCPT ); Sat, 27 Apr 2013 11:56:34 -0400 Content-Disposition: inline In-Reply-To: <20130427132144.GC32432@kroah.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: > The rules for staging are: > - it has to build > - it has to be self-contained in drivers/staging/YOUR_NAME/ > - it has to have a correct license (i.e. GPLv2 compatible). > - it has to have a TODO file listing what needs to be done in > order to get it out of staging. > that's it. Traditionally Lustre needed some patches in fs/* I don't know if that's still the case. But if yes you would likely need to get those in first separately. -Andi -- ak@linux.intel.com -- Speaking for myself only