From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754808Ab0JFEat (ORCPT ); Wed, 6 Oct 2010 00:30:49 -0400 Received: from mail-qw0-f46.google.com ([209.85.216.46]:35051 "EHLO mail-qw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754293Ab0JFEap (ORCPT ); Wed, 6 Oct 2010 00:30:45 -0400 Message-ID: <4CABFB6F.2070800@vflare.org> Date: Wed, 06 Oct 2010 00:30:39 -0400 From: Nitin Gupta User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Greg KH CC: Dave Hansen , Pekka Enberg , Minchan Kim , Andrew Morton , Linux Driver Project , linux-mm , linux-kernel Subject: Re: OOM panics with zram References: <1281374816-904-1-git-send-email-ngupta@vflare.org> <1284053081.7586.7910.camel@nimitz> <4CA8CE45.9040207@vflare.org> <20101005234300.GA14396@kroah.com> <4CABDF0E.3050400@vflare.org> <20101006023624.GA27685@kroah.com> In-Reply-To: <20101006023624.GA27685@kroah.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/5/2010 10:36 PM, Greg KH wrote: > On Tue, Oct 05, 2010 at 10:29:34PM -0400, Nitin Gupta wrote: >> On 10/5/2010 7:43 PM, Greg KH wrote: >>> On Sun, Oct 03, 2010 at 02:41:09PM -0400, Nitin Gupta wrote: >>>> Also, please do not use linux-next/mainline version of compcache. Instead >>>> just use version in the project repository here: >>>> hg clone https://compcache.googlecode.com/hg/ compcache >>> >>> What? No, the reason we put this into the kernel was so that _everyone_ >>> could work on it, including the original developers. Going off and >>> doing development somewhere else just isn't ok. Should I just delete >>> this driver from the staging tree as you don't seem to want to work with >>> the community at this point in time? >>> >> >> Getting it out of -staging wasn't my intent. Community is the reason >> that this project still exists. >> >> >>>> This is updated much more frequently and has many more bug fixes over >>>> the mainline. It will also be easier to fix bugs/add features much more >>>> quickly in this repo rather than sending them to lkml which can take >>>> long time. >>> >>> Yes, developing in your own sandbox can always be faster, but there is >>> no feedback loop. >>> >> >> I was finding it real hard to find time to properly discuss each patch >> over LKML, so I thought of shifting focus to local project repository >> and then later go through proper reviews. > > So, should I delete the version in staging, or are you going to send > patches to sync it up with your development version? > Deleting it from staging would not help much. Much more helpful would be to sync at least the mainline and linux-next version of the driver so it's easier to develop against these kernel trees. Initially, I thought -staging means that any reviewed change can quickly make it to *both* linux-next and more importantly -staging in mainline. Working/ Testing against mainline is much smoother than against linux-next. Thanks, Nitin