All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Nitin Gupta <ngupta@vflare.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Dan Magenheimer <dan.magenheimer@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: Thu, 10 Feb 2011 13:17:01 -0800	[thread overview]
Message-ID: <4D5455CD.3000507@oracle.com> (raw)
In-Reply-To: <4D5454CC.1000609@vflare.org>

On 02/10/11 13:12, Nitin Gupta wrote:
> On 02/11/2011 02:38 AM, Randy Dunlap wrote:
>> On 02/10/11 13:00, 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>
>>
>> Acked-by: Randy Dunlap<randy.dunlap@oracle.com>
>>
>>
>> but what does this patch apply to?  It does not apply cleanly to
>> linux-next of 20110210.
>>
> 
> This applies to staging-2.6. I thought linux-next won't be that
> different so as to produce conflicts. Can you please send reject files,
> or let me fetch linux-next tree and will soon post patch against the same.

I'll let you fetch linux-next.  I merged it by hand and test-built it
successfully.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-02-10 21:17 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 [this message]
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
  -- 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=4D5455CD.3000507@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.