linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, ngupta@vflare.org,
	Konrad Wilk <konrad.wilk@oracle.com>,
	sjenning@linux.vnet.ibm.com, minchan@kernel.org
Subject: RE: [PATCH 0/3] staging: zcache+ramster: move to new code base and re-merge
Date: Thu, 16 Aug 2012 15:53:11 -0700 (PDT)	[thread overview]
Message-ID: <9f2da295-4164-4e95-bbe8-bd234307b83c@default> (raw)
In-Reply-To: <20120816224814.GA18737@kroah.com>

> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Subject: Re: [PATCH 0/3] staging: zcache+ramster: move to new code base and re-merge
> 
> On Thu, Aug 16, 2012 at 03:31:30PM -0700, Dan Magenheimer wrote:
> > Greg, please pull for staging-next.
> 
> Pull what?

Doh!  Sorry, I did that once before and used the same template for the
message.  Silly me, I meant please apply.  Will try again when my
head isn't fried. :-(

> You sent patches, in a format that I can't even apply.
> Consider this email thread deleted :(

Huh?  Can you explain more?  I used git format-patch and git-email
just as for previous patches and even checked the emails with
a trial send to myself.  What is un-apply-able?

Dan

--
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>

  reply	other threads:[~2012-08-16 22:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16 22:31 Dan Magenheimer
2012-08-16 22:31 ` [PATCH 1/3] Remove old zcache and ramster staging drivers to prep for new code base Dan Magenheimer
2012-08-16 22:31 ` [PATCH 2/3] Move to new zcache codebase Dan Magenheimer
2012-08-16 22:31 ` [PATCH 3/3] Move to new codebase for ramster, re-merged with " Dan Magenheimer
2012-08-16 22:48 ` [PATCH 0/3] staging: zcache+ramster: move to new code base and re-merge Greg KH
2012-08-16 22:53   ` Dan Magenheimer [this message]
2012-08-16 23:08     ` Greg KH
2012-08-17  0:19       ` Dan Magenheimer
2012-08-17 22:32       ` Seth Jennings
2012-08-18 19:10         ` 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=9f2da295-4164-4e95-bbe8-bd234307b83c@default \
    --to=dan.magenheimer@oracle.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.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