[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101006140343.GC19470@kroah.com>
Date: Wed, 6 Oct 2010 07:03:43 -0700
From: Greg KH <greg@...ah.com>
To: Pekka Enberg <penberg@...nel.org>
Cc: Nitin Gupta <ngupta@...are.org>,
Dave Hansen <dave@...ux.vnet.ibm.com>,
Pekka Enberg <penberg@...helsinki.fi>,
Minchan Kim <minchan.kim@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Driver Project <devel@...uxdriverproject.org>,
linux-mm <linux-mm@...ck.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: OOM panics with zram
On Wed, Oct 06, 2010 at 10:38:59AM +0300, Pekka Enberg wrote:
> Hi,
>
> On Wed, Oct 6, 2010 at 7:30 AM, Nitin Gupta <ngupta@...are.org> wrote:
> > 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.
>
> We can't push the patches immediately to mainline because we need to
> respect the merge window. You shouldn't need to rely on linux-next for
> testing, though, but work directly against Greg's staging tree. Greg,
> where's the official tree at, btw? The tree at
>
> http://kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
>
> seems empty.
Oops, I need to update the MAINTAINERS file, the proper place for the
staging tree is now in git, at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-next-2.6.git
which feeds directly into the linux-next tree.
hope this helps,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists