Skip to contentSkip to conversation

linux-next still missing patch for zcache modular Kconfig/build issue

DISCUSSION [email protected] 2 participants 3 messages Feb 23, 2011

lore
Share & tools
lore
#0 lore raw

I know this is a known and solved problem with CONFIG_ZCACHE=m I hit a while back:

Building modules, stage 2.
MODPOST 258 modules
ERROR: "xv_malloc" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_new_pool" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_put" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_destroy_pool" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "xv_free" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "xv_get_object_size" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_get" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_flush_object" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_flush_page" [drivers/staging/zcache/zcache.ko] undefined!

The patch for this isn't in the linux-next tree I pulled yesterday - what happened to it?

#1 lore raw
Quoted 23 lines

From: [email protected] [mailto:[email protected]]
Sent: Wednesday, February 23, 2011 1:09 PM
Subject: linux-next still missing patch for zcache modular Kconfig/build issue

I know this is a known and solved problem with CONFIG_ZCACHE=m I hit a while back:

Building modules, stage 2.
MODPOST 258 modules
ERROR: "xv_malloc" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_new_pool" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_put" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_destroy_pool" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "xv_free" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "xv_get_object_size" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_get" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_flush_object" [drivers/staging/zcache/zcache.ko] undefined!
ERROR: "tmem_flush_page" [drivers/staging/zcache/zcache.ko] undefined!

Quoted 2 lines

The patch for this isn't in the linux-next tree I pulled yesterday - what happened to it?

GregKH hasn't yet pulled the fix into staging-next, which feeds into linux-next. See:

https://lkml.org/lkml/2011/2/18/311
https://lkml.org/lkml/2011/2/18/342