From: Greg KH <gregkh@linuxfoundation.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
sjenning@linux.vnet.ibm.com, minchan@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
devel@linuxdriverproject.org, ngupta@vflare.org
Subject: Re: [PATCH 0/3] staging: ramster: move to new zcache2 code base
Date: Tue, 4 Sep 2012 14:38:27 -0700 [thread overview]
Message-ID: <20120904213827.GA12394@kroah.com> (raw)
In-Reply-To: <20120831000020.GA14628@localhost.localdomain>
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.
thanks,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
sjenning@linux.vnet.ibm.com, minchan@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
devel@linuxdriverproject.org, ngupta@vflare.org
Subject: Re: [PATCH 0/3] staging: ramster: move to new zcache2 code base
Date: Tue, 4 Sep 2012 14:38:27 -0700 [thread overview]
Message-ID: <20120904213827.GA12394@kroah.com> (raw)
In-Reply-To: <20120831000020.GA14628@localhost.localdomain>
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.
thanks,
greg k-h
next prev parent reply other threads:[~2012-09-04 21:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 22:46 [PATCH 0/3] staging: ramster: move to new zcache2 code base Dan Magenheimer
2012-08-30 22:46 ` Dan Magenheimer
2012-08-30 22:46 ` [PATCH 1/3] staging: ramster: remove old driver to prep for new base Dan Magenheimer
2012-08-30 22:46 ` Dan Magenheimer
2012-09-05 19:03 ` Greg KH
2012-09-05 19:03 ` Greg KH
2012-08-30 22:46 ` [PATCH 2/3] staging: ramster: move to new zcache2 codebase Dan Magenheimer
2012-08-30 22:46 ` Dan Magenheimer
2012-08-30 22:46 ` [PATCH 3/3] staging: ramster: place ramster codebase on top of " Dan Magenheimer
2012-08-30 22:46 ` Dan Magenheimer
2012-08-31 0:00 ` [PATCH 0/3] staging: ramster: move to new zcache2 code base Konrad Rzeszutek Wilk
2012-08-31 0:00 ` Konrad Rzeszutek Wilk
2012-09-04 21:38 ` Greg KH [this message]
2012-09-04 21:38 ` Greg KH
2012-09-05 11:55 ` Konrad Rzeszutek Wilk
2012-09-05 11:55 ` Konrad Rzeszutek Wilk
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=20120904213827.GA12394@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.magenheimer@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sjenning@linux.vnet.ibm.com \
/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.