[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120514200659.GA15604@kroah.com>
Date: Mon, 14 May 2012 13:06:59 -0700
From: Greg KH <gregkh@...uxfoundation.org>
To: Dan Magenheimer <dan.magenheimer@...cle.com>
Cc: devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, ngupta@...are.org, konrad.wilk@...cle.com,
sjenning@...ux.vnet.ibm.com
Subject: Re: [PATCH] ramster: switch over to zsmalloc and crypto interface
On Thu, May 10, 2012 at 12:06:21PM -0700, Dan Magenheimer wrote:
> RAMster does many zcache-like things. In order to avoid major
> merge conflicts at 3.4, ramster used lzo1x directly for compression
> and retained a local copy of xvmalloc, while zcache moved to the
> new zsmalloc allocator and the crypto API.
>
> This patch moves ramster forward to use zsmalloc and crypto.
>
> Signed-off-by: Dan Magenheimer <dan.magenheimer@...cle.com>
I finally enabled building this one (didn't realize it required ZCACHE
to be disabled, I can only build one or the other), and I noticed after
this patch the following warnings in my build:
drivers/staging/ramster/zcache-main.c:950:13: warning: ‘zcache_do_remotify_ops’ defined but not used [-Wunused-function]
drivers/staging/ramster/zcache-main.c:1039:13: warning: ‘ramster_remotify_init’ defined but not used [-Wunused-function]
drivers/staging/ramster/zcache-main.c: In function ‘zcache_put’:
drivers/staging/ramster/zcache-main.c:1594:4: warning: ‘page’ may be used uninitialized in this function [-Wuninitialized]
drivers/staging/ramster/zcache-main.c:1536:8: note: ‘page’ was declared here
Care to please fix them up?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists