Re: [PATCH] ramster: switch over to zsmalloc and crypto interface
From: Greg KH
Date: Mon May 14 2012 - 16:07:04 EST
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@xxxxxxxxxx>
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?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/