linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, ngupta@vflare.org, konrad.wilk@oracle.com,
	sjenning@linux.vnet.ibm.com, minchan@kernel.org
Subject: Re: [PATCH 1/3] staging: ramster: remove old driver to prep for new base
Date: Wed, 5 Sep 2012 12:03:51 -0700	[thread overview]
Message-ID: <20120905190351.GA21131@kroah.com> (raw)
In-Reply-To: <1346366764-31717-2-git-send-email-dan.magenheimer@oracle.com>

On Thu, Aug 30, 2012 at 03:46:02PM -0700, Dan Magenheimer wrote:
> To prep for moving the ramster codebase on top of the new
> redesigned zcache2 codebase, we remove ramster (as well
> as its contained diverged v1.1 version of zcache) entirely.

This patch fails to apply on top of my staging-next tree :(

Care to refresh it, keep Konrad's ack, and resend all 3?

thanks,

greg k-h

  reply	other threads:[~2012-09-05 19:06 UTC|newest]

Thread overview: 9+ 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 ` [PATCH 1/3] staging: ramster: remove old driver to prep for new base Dan Magenheimer
2012-09-05 19:03   ` Greg KH [this message]
2012-08-30 22:46 ` [PATCH 2/3] staging: ramster: move to new zcache2 codebase Dan Magenheimer
2012-08-30 22:46 ` [PATCH 3/3] staging: ramster: place ramster codebase on top of " Dan Magenheimer
2012-08-31  0:00 ` [PATCH 0/3] staging: ramster: move to new zcache2 code base Konrad Rzeszutek Wilk
2012-09-04 21:38   ` Greg KH
2012-09-05 11:55     ` Konrad Rzeszutek Wilk
2012-09-05 20:44 [PATCH V2 " Dan Magenheimer
2012-09-05 20:44 ` [PATCH 1/3] staging: ramster: remove old driver to prep for new base Dan Magenheimer

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=20120905190351.GA21131@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).