All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Greg KH <greg@kroah.com>
Cc: zbr@ioremap.net, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org, dst@ioremap.net
Subject: Re: [0/7] Distributed storage for drivers/staging merge request
Date: Tue, 13 Jan 2009 16:12:21 -0800	[thread overview]
Message-ID: <20090113161221.b23510b4.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090114000130.GA20811@kroah.com>

On Tue, 13 Jan 2009 16:01:30 -0800
Greg KH <greg@kroah.com> wrote:

> > Really. I implemented all the suggestions I got from the previous
> > reviews (including spaces and documentations, which btw were the only
> > ones :) way too long ago and did not get any other complaints. Actually
> > the tree I sent to you does not contain documentation update I have in
> > the own tree (pointed during review), so this can be added as todo entry :)
> > My fault I found that too late.
> 
> Hm, then why can't this whole thing just go into fs/dst/ right now?
> It's self-contained, so there shouldn't be any special "must live in
> staging" rule for filesystems before adding them.
> 
> We take new drivers at almost any point in the release cycle, why should
> filesystems be any different?

Well...  the case for merging drivers is usually pretty simple - the
hardware exists, so we need the driver.

Whereas the "do we need this" case for new filesystems isn't this simple.

  parent reply	other threads:[~2009-01-14  0:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 23:05 [0/7] Distributed storage for drivers/staging merge request Evgeniy Polyakov
2009-01-13 23:05 ` [1/7] dst: core files Evgeniy Polyakov
2009-01-13 23:05   ` [2/7] dst: network state machine Evgeniy Polyakov
2009-01-13 23:05     ` [3/7] dst: export node Evgeniy Polyakov
2009-01-13 23:05       ` [4/7] dst: thread pool Evgeniy Polyakov
2009-01-13 23:05         ` [5/7] dst: transactions Evgeniy Polyakov
2009-01-13 23:05           ` [6/7] dst: crypto processing Evgeniy Polyakov
2009-01-13 23:05             ` [7/7] dst: kconfig and makefile changes Evgeniy Polyakov
2009-01-13 23:09               ` [8/7] dst: kconfig update Evgeniy Polyakov
2009-01-14  2:22                 ` Randy Dunlap
2009-01-14  9:09                   ` Evgeniy Polyakov
2009-01-14  2:22               ` [7/7] dst: kconfig and makefile changes Randy Dunlap
2009-01-14 14:46         ` [4/7] dst: thread pool Frederik Deweerdt
2009-01-14 15:01           ` Evgeniy Polyakov
2009-01-15  5:58         ` Andrew Morton
2009-01-15  8:47           ` Evgeniy Polyakov
2009-01-19  0:10           ` Arjan van de Ven
2009-01-19 17:07             ` Evgeniy Polyakov
2009-02-05 13:55             ` David Howells
2009-01-14 14:52       ` [3/7] dst: export node Jens Axboe
2009-01-14 15:11         ` Evgeniy Polyakov
2009-01-13 23:39 ` [0/7] Distributed storage for drivers/staging merge request Greg KH
2009-01-13 23:47   ` Evgeniy Polyakov
2009-01-14  0:01     ` Greg KH
2009-01-14  0:08       ` Evgeniy Polyakov
2009-01-14  0:12       ` Andrew Morton [this message]
2009-01-14  0:15         ` Evgeniy Polyakov
2009-01-14  0:20           ` Evgeniy Polyakov
2009-01-14  0:23             ` Andrew Morton
2009-01-14  0:24               ` Evgeniy Polyakov
2009-01-14  9:39               ` Jeff Garzik

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=20090113161221.b23510b4.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dst@ioremap.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zbr@ioremap.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 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.