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? thanks, greg k-h -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>