[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090917133846.a00daece.akpm@linux-foundation.org>
Date: Thu, 17 Sep 2009 13:38:46 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Oleg Nesterov <oleg@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
menage@...gle.com, bblum@...gle.com, ebiederm@...ssion.com,
lizf@...fujitsu.com, matthltc@...ibm.com
Subject: Re: cgrooups && 2.6.32 -mm merge plans
On Thu, 17 Sep 2009 22:15:16 +0200
Oleg Nesterov <oleg@...hat.com> wrote:
> On 09/15, Andrew Morton wrote:
> >
> > #cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup.patch: Oleg conniptions
> > cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup.patch
> > cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup-fix.patch
> > cgroups-add-ability-to-move-all-threads-in-a-process-to-a-new-cgroup-atomically.patch
> >
> > Merge after checking with Oleg.
>
> Well. I think these patches are buggy :/
>
Well that's never prevented us from merging stuff before.
Thanks, I'll disable the patches for now. Do we have a grip on what's
wrong and what needs to be done to fix things?
--
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