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 2/3] staging: ramster: move to new zcache2 codebase
Date: Wed, 5 Sep 2012 17:07:08 -0700 [thread overview]
Message-ID: <20120906000708.GA13754@kroah.com> (raw)
In-Reply-To: <1346877901-12543-3-git-send-email-dan.magenheimer@oracle.com>
On Wed, Sep 05, 2012 at 01:45:00PM -0700, Dan Magenheimer wrote:
> [V2: rebased to apply to 20120905 staging-next, no other changes]
You do realize this patch introduces build warnings, right?
Hopefully you will fix that up soon (i.e. really soon...)
greg k-h
next prev parent reply other threads:[~2012-09-06 0:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 20:44 [PATCH V2 0/3] staging: ramster: move to new zcache2 code base Dan Magenheimer
2012-09-05 20:44 ` [PATCH 1/3] staging: ramster: remove old driver to prep for new base Dan Magenheimer
2012-09-05 20:45 ` [PATCH 2/3] staging: ramster: move to new zcache2 codebase Dan Magenheimer
2012-09-06 0:07 ` Greg KH [this message]
2012-12-28 19:59 ` Geert Uytterhoeven
2013-01-02 21:41 ` Konrad Rzeszutek Wilk
2012-09-05 20:45 ` [PATCH 3/3] staging: ramster: place ramster codebase on top of " Dan Magenheimer
2012-09-06 0:14 ` [PATCH V2 0/3] staging: ramster: move to new zcache2 code base Greg KH
-- strict thread matches above, loose matches on Subject: below --
2012-08-30 22:46 [PATCH " Dan Magenheimer
2012-08-30 22:46 ` [PATCH 2/3] staging: ramster: move to new zcache2 codebase 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=20120906000708.GA13754@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).