From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, linux-mm@kvack.org,
ngupta@vflare.org, konrad.wilk@oracle.com,
sjenning@linux.vnet.ibm.com, minchan@kernel.org,
dan.magenheimer@oracle.com
Subject: [PATCH 1/5] staging: ramster: disable build in anticipation of renaming
Date: Fri, 18 Jan 2013 13:24:23 -0800 [thread overview]
Message-ID: <1358544267-9104-2-git-send-email-dan.magenheimer@oracle.com> (raw)
In-Reply-To: <1358544267-9104-1-git-send-email-dan.magenheimer@oracle.com>
[V2: no code changes, patchset now generated via git format-patch -M]
In staging, disable ramster build in anticipation of renaming to zcache
Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>
---
drivers/staging/Kconfig | 2 --
drivers/staging/Makefile | 1 -
2 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/Kconfig b/drivers/staging/Kconfig
index db8a512..eb61455 100644
--- a/drivers/staging/Kconfig
+++ b/drivers/staging/Kconfig
@@ -126,8 +126,6 @@ source "drivers/staging/csr/Kconfig"
source "drivers/staging/omap-thermal/Kconfig"
-source "drivers/staging/ramster/Kconfig"
-
source "drivers/staging/silicom/Kconfig"
source "drivers/staging/ced1401/Kconfig"
diff --git a/drivers/staging/Makefile b/drivers/staging/Makefile
index a9d5479..18420b8 100644
--- a/drivers/staging/Makefile
+++ b/drivers/staging/Makefile
@@ -55,7 +55,6 @@ obj-$(CONFIG_USB_G_CCG) += ccg/
obj-$(CONFIG_WIMAX_GDM72XX) += gdm72xx/
obj-$(CONFIG_CSR_WIFI) += csr/
obj-$(CONFIG_OMAP_BANDGAP) += omap-thermal/
-obj-$(CONFIG_ZCACHE2) += ramster/
obj-$(CONFIG_NET_VENDOR_SILICOM) += silicom/
obj-$(CONFIG_CED1401) += ced1401/
obj-$(CONFIG_DRM_IMX) += imx-drm/
--
1.7.1
--
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>
next prev parent reply other threads:[~2013-01-18 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 21:24 [PATCH V2 0/5] staging: zcache: move new zcache code base from ramster Dan Magenheimer
2013-01-18 21:24 ` Dan Magenheimer [this message]
2013-01-18 21:24 ` [PATCH 2/5] staging: zcache: rename ramster to zcache Dan Magenheimer
2013-01-19 19:57 ` Dan Carpenter
2013-01-22 17:04 ` Dan Magenheimer
2013-01-18 21:24 ` [PATCH 3/5] staging: zcache: adjustments to config/build files due to renaming Dan Magenheimer
2013-01-18 21:24 ` [PATCH 4/5] staging: zcache: re-enable config/build of zcache after renaming Dan Magenheimer
2013-01-18 21:24 ` [PATCH 5/5] staging: zcache: fix uninitialized variable compile warning Dan Magenheimer
2013-01-18 21:46 ` [PATCH V2 0/5] staging: zcache: move new zcache code base from ramster Greg KH
2013-01-18 21:56 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2013-01-17 17:26 [PATCH " Dan Magenheimer
2013-01-17 17:26 ` [PATCH 1/5] staging: ramster: disable build in anticipation of renaming 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=1358544267-9104-2-git-send-email-dan.magenheimer@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).