From: Nitin Gupta <ngupta@vflare.org>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Allow sharing xvmalloc for zram and zcache
Date: Sat, 19 Feb 2011 04:05:38 +0530 [thread overview]
Message-ID: <4D5EF43A.5040905@vflare.org> (raw)
In-Reply-To: <20110218212542.GI796@kroah.com>
On 02/19/2011 02:55 AM, Greg KH wrote:
> On Thu, Feb 10, 2011 at 04:00:46PM -0500, Nitin Gupta wrote:
>> Both zram and zcache use xvmalloc allocator. If xvmalloc
>> is compiled separately for both of them, we will get linker
>> error if they are both selected as "built-in". We can also
>> get linker error regarding missing xvmalloc symbols if zram
>> is not built.
>>
>> So, we now compile xvmalloc separately and export its symbols
>> which are then used by both of zram and zcache.
>>
>> Signed-off-by: Nitin Gupta<ngupta@vflare.org>
>
> This doesn't apply to my tree, care to respin it and resend?
>
The new patch:
https://lkml.org/lkml/2011/2/18/340
applies to staging-next branch of the staging-2.6 tree.
Thanks,
Nitin
next prev parent reply other threads:[~2011-02-18 22:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 21:00 [PATCH] Allow sharing xvmalloc for zram and zcache Nitin Gupta
2011-02-10 21:08 ` Randy Dunlap
2011-02-10 21:12 ` Nitin Gupta
2011-02-10 21:17 ` Randy Dunlap
2011-02-10 21:20 ` Nitin Gupta
2011-02-10 21:26 ` Randy Dunlap
2011-02-18 21:25 ` Greg KH
2011-02-18 22:35 ` Nitin Gupta [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-18 22:33 Nitin Gupta
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=4D5EF43A.5040905@vflare.org \
--to=ngupta@vflare.org \
--cc=dan.magenheimer@oracle.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).