Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753484AbbHRVBv (ORCPT ); Tue, 18 Aug 2015 17:01:51 -0400 Received: from mail-pd0-f182.google.com ([209.85.192.182]:35209 "EHLO mail-pd0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753388AbbHRVBs (ORCPT ); Tue, 18 Aug 2015 17:01:48 -0400 Date: Tue, 18 Aug 2015 14:01:45 -0700 From: Tejun Heo To: axboe@kernel.dk Cc: vgoyal@redhat.com, linux-kernel@vger.kernel.org, avanzini.arianna@gmail.com, kernel-team@fb.com, hannes@cmpxchg.org, lizefan@huawei.com, cgroups@vger.kernel.org Subject: Re: [PATCH v2 02/10] cgroup: introduce cgroup_subsys->legacy_name Message-ID: <20150818210145.GE15739@mtj.duckdns.org> References: <1437763434-28699-1-git-send-email-tj@kernel.org> <1437763434-28699-3-git-send-email-tj@kernel.org> <20150728175647.GH5322@mtj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150728175647.GH5322@mtj.duckdns.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 974 Lines: 27 On Tue, Jul 28, 2015 at 01:56:47PM -0400, Tejun Heo wrote: > This allows cgroup subsystems to use a different name on the unified > hierarchy. cgroup_subsys->name is used on the unified hierarchy, > ->legacy_name elsewhere. If ->legacy_name is not explicitly set, it's > automatically set to ->name and the userland visible behavior remains > unchanged. > > v2: Make parse_cgroupfs_options() only consider ->legacy_name as mount > options are used only on legacy hierarchies. Suggested by Li > Zefan. > > Signed-off-by: Tejun Heo > Cc: Li Zefan > Cc: Johannes Weiner > Cc: cgroups@vger.kernel.org Applied to cgroup/for-4.3-unified-base. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/