[PATCH 0/3] staging: ramster: move to new zcache2 code base

[Konrad Rzeszutek Wilk]

On Tue, Sep 04, 2012 at 02:38:27PM -0700, Greg KH wrote:
> On Thu, Aug 30, 2012 at 08:00:20PM -0400, Konrad Rzeszutek Wilk wrote:
> > On Thu, Aug 30, 2012 at 03:46:01PM -0700, Dan Magenheimer wrote:
> > > Hi Greg --
> > > 
> > > gregkh> If you feel that the existing code needs to be dropped
> > > gregkh> and replaced with a totally new version, that's fine with
> > > gregkh> me.  It's forward progress, which is all that I ask for. 
> > > (http://lkml.indiana.edu/hypermail/linux/kernel/1208.0/02240.html,
> > > in reference to zcache, assuming applies to ramster as well)
> > > 
> > > Please apply for staging-next for the 3.7 window to move ramster forward.
> > > Since AFAICT there have been no patches or contributions from others to
> > > drivers/staging/ramster since it was merged, this totally new version
> > > of ramster should not run afoul and the patches should apply to
> > > 3.5 or 3.6-rcN.
> > > 
> > > Thanks,
> > > Dan
> > > 
> > > When ramster was merged into staging at 3.4, it used a "temporarily" forked
> > > version of zcache.  Code was proposed to merge zcache and ramster into
> > > a new common redesigned codebase which both resolves various serious design
> > > flaws and eliminates all code duplication between zcache and ramster, with
> > > the result to replace "zcache".  Sadly, that proposal was blocked, so the
> > > zcache (and tmem) code in drivers/staging/zcache and the zcache (and tmem)
> > > code in drivers/staging/ramster continue to be different.
> > 
> > Right. They will diverge for now.
> 
> Konrad, can I get your Acked-by: for this series?  I need that before I
> can apply it.

Acked-by: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com>
> 
> thanks,
> 
> greg k-h