From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Subject: Re: Mainlining Lustre client Date: Sat, 27 Apr 2013 06:21:44 -0700 Message-ID: <20130427132144.GC32432@kroah.com> References: <1882637210201641A747464075FFC649025BEEEA@MX101CL02.corp.emc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Al Viro , "linux-fsdevel@vger.kernel.org" , Christoph Hellwig , Andreas Dilger , Matthew Wilcox , Andi Kleen , Theodore Ts'o , "Myklebust, Trond" , "faibish, sorin" , "Tang, Haiying" To: "Peng, Tao" Return-path: Received: from mail-pa0-f53.google.com ([209.85.220.53]:47155 "EHLO mail-pa0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753038Ab3D0NVq (ORCPT ); Sat, 27 Apr 2013 09:21:46 -0400 Received: by mail-pa0-f53.google.com with SMTP id kx1so36034pab.12 for ; Sat, 27 Apr 2013 06:21:46 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1882637210201641A747464075FFC649025BEEEA@MX101CL02.corp.emc.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sat, Apr 27, 2013 at 03:33:26AM +0000, Peng, Tao wrote: > Now, we would want to ask for your favor on how we can put the code in > staging tree. What are the requirements for being merged in the > staging tree? Shall we send the huge patches for review? Which merge > window shall we target at? And any other issues you have in mind. > Please share your thoughts. Thank you very much! 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. So make up a big patch, keeping everything in drivers/staging/lustre/ and send it to me and we can go from there. thanks, greg k-h