[PATCH] ramster: switch over to zsmalloc and crypto interface

Greg KH gregkh at linuxfoundation.org
Mon May 14 20:06:59 UTC 2012

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 at oracle.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?


greg k-h

More information about the devel mailing list