[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160102115257.GD3660@htj.duckdns.org>
Date: Sat, 2 Jan 2016 06:52:57 -0500
From: Tejun Heo <tj@...nel.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: "Serge E. Hallyn" <serge.hallyn@...ntu.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-api@...r.kernel.org, containers@...ts.linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
lxc-devel@...ts.linuxcontainers.org,
Johannes Weiner <hannes@...xchg.org>, cgroups@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: CGroup Namespaces (v8)
On Fri, Jan 01, 2016 at 11:14:14AM -0800, Dan Williams wrote:
> On Fri, Jan 1, 2016 at 10:06 AM, Serge E. Hallyn
> <serge.hallyn@...ntu.com> wrote:
> > On Fri, Jan 01, 2016 at 01:42:57AM -0800, Dan Williams wrote:
> >> Commit 54b39d263704 "cgroup: cgroup namespace setns support" not
> >> booting is a separate issue.
> >
> > Oh - been there since my first version of the set (v4). Odd, I
> > thought that the automated korg testing caught those.
> >
> > What is the simplest way to fix this? Do I send new versions of
> > patches v3 and v4? Does Tejun or Stephen just do it inline in the
> > git tree? Do we leave it be?
>
> I'm assuming it can be fixed up when you re-spin the patches to fix
> the boot failure.
I reverted the cgroup namespace patchset for the time being.
Thanks.
--
tejun
--
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