[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090114000839.GA512@ioremap.net>
Date: Wed, 14 Jan 2009 03:08:39 +0300
From: Evgeniy Polyakov <zbr@...emap.net>
To: Greg KH <greg@...ah.com>
Cc: torvalds@...ux-foundation.org,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, dst@...emap.net
Subject: Re: [0/7] Distributed storage for drivers/staging merge request
On Tue, Jan 13, 2009 at 04:01:30PM -0800, Greg KH (greg@...ah.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.
Its a block device not a filesystem, so it is more like a driver.
All original patches placed it into the drivers/block/dst without touch
any external files except makefile and kconfig.
> We take new drivers at almost any point in the release cycle, why should
> filesystems be any different?
I suppose this is a rethorical question, since there is no answer :)
> Linus, Andrew, any objections?
Hi there!
--
Evgeniy Polyakov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists