From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757140Ab1BJVMJ (ORCPT ); Thu, 10 Feb 2011 16:12:09 -0500 Received: from mail-vx0-f174.google.com ([209.85.220.174]:45463 "EHLO mail-vx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756993Ab1BJVMI (ORCPT ); Thu, 10 Feb 2011 16:12:08 -0500 Message-ID: <4D5454CC.1000609@vflare.org> Date: Fri, 11 Feb 2011 02:42:44 +0530 From: Nitin Gupta User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7 MIME-Version: 1.0 To: Randy Dunlap 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> In-Reply-To: <4D5453CB.7050206@oracle.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Thanks, Nitin