From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Peng, Tao" <tao.peng@emc.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Andreas Dilger <adilger@dilger.ca>,
Matthew Wilcox <willy@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>, Theodore Ts'o <tytso@mit.edu>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"faibish, sorin" <faibish_sorin@emc.com>,
"Tang, Haiying" <haiying.tang@emc.com>
Subject: Re: Mainlining Lustre client
Date: Sat, 27 Apr 2013 06:21:44 -0700 [thread overview]
Message-ID: <20130427132144.GC32432@kroah.com> (raw)
In-Reply-To: <1882637210201641A747464075FFC649025BEEEA@MX101CL02.corp.emc.com>
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
next prev parent reply other threads:[~2013-04-27 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 3:33 Mainlining Lustre client Peng, Tao
2013-04-27 13:21 ` Greg Kroah-Hartman [this message]
2013-04-27 14:39 ` Peng Tao
2013-04-27 15:56 ` Andi Kleen
2013-04-27 16:12 ` Peng Tao
2013-04-27 19:09 ` Andreas Dilger
2013-04-28 2:54 ` Peng Tao
2013-04-29 2:46 ` Greg Kroah-Hartman
2013-04-30 14:04 ` Peng Tao
2013-04-30 21:20 ` J. Bruce Fields
2013-04-30 22:11 ` faibish, sorin
2013-04-30 22:29 ` faibish, sorin
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=20130427132144.GC32432@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Trond.Myklebust@netapp.com \
--cc=adilger@dilger.ca \
--cc=ak@linux.intel.com \
--cc=faibish_sorin@emc.com \
--cc=haiying.tang@emc.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tao.peng@emc.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.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).