From: Greg KH <gregkh@suse.de>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Marcus Klemm <marcus.klemm@googlemail.com>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Konrad Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
kvm@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH v2] staging: zcache: support multiple clients, prep for KVM and RAMster
Date: Thu, 30 Jun 2011 12:23:22 -0700 [thread overview]
Message-ID: <20110630192322.GA1753@suse.de> (raw)
In-Reply-To: <1d15f28a-56df-4cf4-9dd9-1032f211c0d0@default>
On Thu, Jun 30, 2011 at 12:01:08PM -0700, Dan Magenheimer wrote:
> Hi Greg --
>
> I think this patch is now ready for staging-next and for merging when
> the 3.1 window opens. Please let me know if you need any logistics
> done differently.
Ok, thanks, I'll queue it up later this week for 3.1
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Marcus Klemm <marcus.klemm@googlemail.com>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Konrad Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
kvm@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH v2] staging: zcache: support multiple clients, prep for KVM and RAMster
Date: Thu, 30 Jun 2011 12:23:22 -0700 [thread overview]
Message-ID: <20110630192322.GA1753@suse.de> (raw)
In-Reply-To: <1d15f28a-56df-4cf4-9dd9-1032f211c0d0@default>
On Thu, Jun 30, 2011 at 12:01:08PM -0700, Dan Magenheimer wrote:
> Hi Greg --
>
> I think this patch is now ready for staging-next and for merging when
> the 3.1 window opens. Please let me know if you need any logistics
> done differently.
Ok, thanks, I'll queue it up later this week for 3.1
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-06-30 19:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 19:01 [PATCH v2] staging: zcache: support multiple clients, prep for KVM and RAMster Dan Magenheimer
2011-06-30 19:01 ` Dan Magenheimer
2011-06-30 19:23 ` Greg KH [this message]
2011-06-30 19:23 ` Greg KH
2011-06-30 22:40 ` Dan Carpenter
2011-06-30 22:40 ` Dan Carpenter
2011-06-30 22:40 ` Dan Carpenter
2011-06-30 23:28 ` Dan Magenheimer
2011-06-30 23:28 ` Dan Magenheimer
2011-07-01 8:38 ` Dan Carpenter
2011-07-01 8:38 ` Dan Carpenter
2011-07-01 14:31 ` Dan Magenheimer
2011-07-01 14:31 ` Dan Magenheimer
2011-07-01 16:58 ` Dan Carpenter
2011-07-01 16:58 ` Dan Carpenter
2011-07-06 3:30 ` Greg KH
2011-07-06 3:30 ` Greg KH
2011-08-10 14:21 ` Seth Jennings
2011-08-10 14:21 ` Seth Jennings
2011-08-10 14:44 ` Seth Jennings
2011-08-10 14:44 ` Seth Jennings
2011-08-10 15:08 ` Dan Magenheimer
2011-08-10 15:08 ` Dan Magenheimer
2011-08-10 15:40 ` Seth Jennings
2011-08-10 15:40 ` Seth Jennings
[not found] <1d15f28a-56df-4cf4-9dd9-1032f211c0d0@default20110630224019.GC2544@shale.localdomain>
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=20110630192322.GA1753@suse.de \
--to=gregkh@suse.de \
--cc=dan.magenheimer@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcus.klemm@googlemail.com \
--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.