From: "J. Bruce Fields" <bfields@fieldses.org>
To: Peng Tao <tao.peng@emc.com>
Cc: Andi Kleen <ak@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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>,
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: Tue, 30 Apr 2013 17:20:55 -0400 [thread overview]
Message-ID: <20130430212055.GB28641@fieldses.org> (raw)
In-Reply-To: <CA+a=Yy54c7YnGcF+kUuSW7Amh6ODo=+73GPO2Xhz-Uej5FgX=Q@mail.gmail.com>
On Sun, Apr 28, 2013 at 12:12:27AM +0800, Peng Tao wrote:
> On Sat, Apr 27, 2013 at 11:56 PM, Andi Kleen <ak@linux.intel.com> wrote:
> >> 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.
> >
> Those are only needed for Lustre server now. For client, there is no
> need to patch other parts out side of fs/lustre and net/lnet.
The Lustre server is in kernel? Are there plans to mainline that?
If not, what does someone need to get to test the client?
--b.
next prev parent reply other threads:[~2013-04-30 21: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
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 [this message]
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=20130430212055.GB28641@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=adilger@dilger.ca \
--cc=ak@linux.intel.com \
--cc=faibish_sorin@emc.com \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.