From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758567Ab0JFD3d (ORCPT ); Tue, 5 Oct 2010 23:29:33 -0400 Received: from kroah.org ([198.145.64.141]:55098 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752980Ab0JFD3c (ORCPT ); Tue, 5 Oct 2010 23:29:32 -0400 Date: Tue, 5 Oct 2010 19:36:24 -0700 From: Greg KH To: Nitin Gupta Cc: Dave Hansen , Pekka Enberg , Minchan Kim , Andrew Morton , Linux Driver Project , linux-mm , linux-kernel Subject: Re: OOM panics with zram Message-ID: <20101006023624.GA27685@kroah.com> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CABDF0E.3050400@vflare.org> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? thanks, greg k-h