From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Valdis.Kletnieks@vt.edu, Stephen Rothwell <sfr@canb.auug.org.au>,
Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Nitin Gupta <ngupta@vflare.org>
Subject: RE: linux-next still missing patch for zcache modular Kconfig/build issue
Date: Wed, 23 Feb 2011 12:23:34 -0800 (PST) [thread overview]
Message-ID: <fc9a9123-cc27-4754-9222-796890553ee6@default> (raw)
In-Reply-To: <21508.1298491740@localhost>
> From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
> 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!
>
> 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
next prev parent reply other threads:[~2011-02-23 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 20:09 Valdis.Kletnieks
2011-02-23 20:23 ` Dan Magenheimer [this message]
2011-02-23 20:39 ` Valdis.Kletnieks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc9a9123-cc27-4754-9222-796890553ee6@default \
--to=dan.magenheimer@oracle.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®