All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Paul Menage <menage@google.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Containers <containers@lists.linux-foundation.org>
Subject: Re: [PATCH] cgroups: consolidate cgroup documents
Date: Sat, 10 Jan 2009 04:04:42 +0530	[thread overview]
Message-ID: <20090109223442.GO9737@balbir.in.ibm.com> (raw)
In-Reply-To: <4966B383.3030106@cn.fujitsu.com>

* Li Zefan <lizf@cn.fujitsu.com> [2009-01-09 10:16:35]:

> Move Documentation/cpusets.txt and Documentation/controllers/* to
> Documentation/cgroups/
> 
> This inlined patch is generated with git-show -M (rename detected)
> and is for review, and the attached one is for apply.
> 
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
>  Documentation/cgroups/cgroups.txt            |    5 +++--
>  Documentation/cgroups/memcg_test.txt         |    2 +-
>  Documentation/scheduler/sched-design-CFS.txt |    2 +-
>  include/linux/res_counter.h                  |    2 +-
>  init/Kconfig                                 |    9 ++++-----
>  kernel/cpuset.c                              |    2 +-
>  11 files changed, 11 insertions(+), 11 deletions(-)
> 
>  rename Documentation/{controllers => cgroups}/cpuacct.txt (100%)
>  rename Documentation/{ => cgroups}/cpusets.txt (100%)
>  rename Documentation/{controllers => cgroups}/devices.txt (100%)
>  rename Documentation/{controllers => cgroups}/memcg_test.txt (99%)
>  rename Documentation/{controllers => cgroups}/memory.txt (100%)
>  rename Documentation/{controllers => cgroups}/resource_counter.txt (100%)
> 
> diff --git a/Documentation/cgroups/cgroups.txt b/Documentation/cgroups/cgroups.txt
> index e33ee74..d9e5d6f 100644

I think it is a good idea to consolidate it all in one place.

Acked-by: Balbir Singh <balbir@linux.vnet.ibm.com>

-- 
	Balbir

  parent reply	other threads:[~2009-01-09 22:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09  2:16 [PATCH] cgroups: consolidate cgroup documents Li Zefan
     [not found] ` <4966B383.3030106-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-01-09  2:29   ` KAMEZAWA Hiroyuki
2009-01-09 21:19   ` Paul Menage
2009-01-09 22:34   ` Balbir Singh
2009-01-09  2:29 ` KAMEZAWA Hiroyuki
     [not found]   ` <20090109112904.a002ff72.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2009-01-09  6:05     ` Balbir Singh
2009-01-09  6:06     ` Balbir Singh
2009-01-09  6:06   ` Balbir Singh
2009-01-09 21:19 ` Paul Menage
2009-01-09 22:34 ` Balbir Singh [this message]
2009-01-10  0:19   ` Randy Dunlap
     [not found]     ` <20090109161947.70f6d73d.rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2009-01-10  0:25       ` Paul Menage
2009-01-10  0:25         ` Paul Menage
     [not found]   ` <20090109223442.GO9737-SINUvgVNF2CyUtPGxGje5AC/G2K4zDHf@public.gmane.org>
2009-01-10  0:19     ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2009-01-09  2:16 Li Zefan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090109223442.GO9737@balbir.in.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=menage@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.