[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d4f82064-71ba-4712-b831-6499180589b9@default>
Date: Mon, 6 Aug 2012 09:38:52 -0700 (PDT)
From: Dan Magenheimer <dan.magenheimer@...cle.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Pekka Enberg <penberg@...nel.org>,
Minchan Kim <minchan@...nel.org>,
Konrad Wilk <konrad.wilk@...cle.com>,
devel@...verdev.osuosl.org,
Seth Jennings <sjenning@...ux.vnet.ibm.com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Konrad Rzeszutek Wilk <konrad@...nok.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Robert Jennings <rcj@...ux.vnet.ibm.com>,
Nitin Gupta <ngupta@...are.org>
Subject: RE: [PATCH 0/4] promote zcache from staging
> From: Greg Kroah-Hartman [mailto:gregkh@...uxfoundation.org]
> Subject: Re: [PATCH 0/4] promote zcache from staging
>
> On Mon, Aug 06, 2012 at 09:21:22AM -0700, Dan Magenheimer wrote:
> > I suppose:
> >
> > (E) replace "demo" zcache with new code base and keep it
> > in staging for another cycle
> >
> > is another alternative, but I think gregkh has said no to that.
>
> No I have not. If you all feel that the existing code needs to be
> dropped and replaced with a totally new version, that's fine with me.
> It's forward progress, which is all that I ask for.
>
> Hope this helps,
> greg k-h
Hi Greg --
Cool! I guess I mistakenly assumed that your "no new features"
requirement also implied "no fixes of fundamental design flaws". :-)
Having option (E) should make it easier to decide the best
technical solution, separate from the promotion timing and "where
does it land" question.
We'll get back to you soon...
Thanks!
Dan
--
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