From: Greg KH <greg@kroah.com>
To: Sage Weil <sage@newdream.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 00/21] ceph: Ceph distributed file system client v0.9
Date: Fri, 19 Jun 2009 15:44:03 -0700 [thread overview]
Message-ID: <20090619224403.GA27322@kroah.com> (raw)
In-Reply-To: <1245450702-31343-1-git-send-email-sage@newdream.net>
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).
>
> Greg, the first patch in the series creates an fs/staging/ directory.
> This is analogous to drivers/staging/ (not built by allyesconfig,
> modpost will mark the module with 'staging', etc.), except you can
> find it under the File Systems section (and it doesn't get hidden
> along with drivers/ on UML).
>
> If that looks reasonable, I would love to see this go into the staging
> tree. The remaining patches add Ceph at fs/staging/ceph.
No, please put "staging" filesystems at drivers/staging/ where the other
filesystems that are in "staging" shape are.
This is due to some core changes needed to mark such modules as
"TAINT_CRAP", and to make it obvious who is to blame for such crap :)
Care to respin your patches to put the code in drivers/staging/ instead
please?
thanks,
greg k-h
next prev parent reply other threads:[~2009-06-19 22:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 22:31 [PATCH 00/21] ceph: Ceph distributed file system client v0.9 Sage Weil
2009-06-19 22:31 ` [PATCH 01/21] fs: add fs/staging directory Sage Weil
2009-06-19 22:31 ` [PATCH 02/21] ceph: documentation Sage Weil
2009-06-19 22:31 ` [PATCH 03/21] ceph: on-wire types Sage Weil
2009-06-19 22:31 ` [PATCH 04/21] ceph: client types Sage Weil
2009-06-19 22:31 ` [PATCH 05/21] ceph: super.c Sage Weil
2009-06-19 22:31 ` [PATCH 06/21] ceph: inode operations Sage Weil
2009-06-19 22:31 ` [PATCH 07/21] ceph: directory operations Sage Weil
2009-06-19 22:31 ` [PATCH 08/21] ceph: file operations Sage Weil
2009-06-19 22:31 ` [PATCH 09/21] ceph: address space operations Sage Weil
2009-06-19 22:31 ` [PATCH 10/21] ceph: MDS client Sage Weil
2009-06-19 22:31 ` [PATCH 11/21] ceph: OSD client Sage Weil
2009-06-19 22:31 ` [PATCH 12/21] ceph: CRUSH mapping algorithm Sage Weil
2009-06-19 22:31 ` [PATCH 13/21] ceph: monitor client Sage Weil
2009-06-19 22:31 ` [PATCH 14/21] ceph: capability management Sage Weil
2009-06-19 22:31 ` [PATCH 15/21] ceph: snapshot management Sage Weil
2009-06-19 22:31 ` [PATCH 16/21] ceph: messenger library Sage Weil
2009-06-19 22:31 ` [PATCH 17/21] ceph: nfs re-export support Sage Weil
2009-06-19 22:31 ` [PATCH 18/21] ceph: ioctls Sage Weil
2009-06-19 22:31 ` [PATCH 19/21] ceph: debugging Sage Weil
2009-06-19 22:31 ` [PATCH 20/21] ceph: debugfs Sage Weil
2009-06-19 22:31 ` [PATCH 21/21] ceph: Kconfig, Makefile Sage Weil
2009-06-20 9:12 ` [PATCH 17/21] ceph: nfs re-export support Stefan Richter
2009-06-20 20:39 ` Sage Weil
2009-06-20 21:22 ` Stefan Richter
2009-06-19 22:44 ` Greg KH [this message]
2009-06-19 23:15 ` [PATCH 00/21] ceph: Ceph distributed file system client v0.9 Sage Weil
2009-06-19 23:20 ` Greg KH
2009-06-19 22:45 ` Greg KH
2009-06-19 22:54 ` Stephen Rothwell
2009-06-19 23:12 ` Sage Weil
2009-06-19 23:19 ` Greg KH
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=20090619224403.GA27322@kroah.com \
--to=greg@kroah.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@newdream.net \
/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).