Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756882Ab1BJVRX (ORCPT ); Thu, 10 Feb 2011 16:17:23 -0500 Received: from rcsinet10.oracle.com ([148.87.113.121]:23464 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751296Ab1BJVRW (ORCPT ); Thu, 10 Feb 2011 16:17:22 -0500 Message-ID: <4D5455CD.3000507@oracle.com> Date: Thu, 10 Feb 2011 13:17:01 -0800 From: Randy Dunlap Organization: Oracle Linux Engineering User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-3.fc11 Thunderbird/3.0 MIME-Version: 1.0 To: Nitin Gupta CC: Stephen Rothwell , Dan Magenheimer , linux-next , linux-kernel Subject: Re: [PATCH] Allow sharing xvmalloc for zram and zcache References: <1297371646-11604-1-git-send-email-ngupta@vflare.org> <4D5453CB.7050206@oracle.com> <4D5454CC.1000609@vflare.org> In-Reply-To: <4D5454CC.1000609@vflare.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Source-IP: acsmt353.oracle.com [141.146.40.153] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090204.4D5455DB.01B8:SCFMA4539814,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1368 Lines: 36 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 >> >> Acked-by: Randy Dunlap >> >> >> 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 *** -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/