From: Li Zefan <lizf@cn.fujitsu.com>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org,
kamezawa.hiroyu@jp.fujitsu.com, rdunlap@xenotime.net
Subject: Re: [PATCH] trivial: fix where cgroup documentation is not correctly referred to
Date: Wed, 04 Feb 2009 09:09:47 +0800 [thread overview]
Message-ID: <4988EADB.4050508@cn.fujitsu.com> (raw)
In-Reply-To: <1233694085-23893-1-git-send-email-cascardo@holoscopio.com>
Thadeu Lima de Souza Cascardo wrote:
> cgroup documentation was moved to Documentation/cgroups/. There are some
> places that still refer to Documentation/controllers/,
> Documentation/cgroups.txt and Documentation/cpusets.txt. Fix those.
>
After grep, I think there's no wrong ref anymore.
Reviewed-by: Li Zefan <lizf@cn.fujitsu.com>
> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
> ---
> Documentation/00-INDEX | 4 ++--
> Documentation/cgroups/00-INDEX | 18 ++++++++++++++++++
> Documentation/kernel-parameters.txt | 4 ++--
> Documentation/scheduler/sched-rt-group.txt | 2 +-
> Documentation/vm/numa_memory_policy.txt | 3 ++-
> Documentation/vm/page_migration | 3 ++-
> Documentation/x86/x86_64/fake-numa-for-cpusets | 5 +++--
> include/linux/cgroup.h | 5 ++++-
> init/Kconfig | 2 +-
> 9 files changed, 35 insertions(+), 11 deletions(-)
> create mode 100644 Documentation/cgroups/00-INDEX
next prev parent reply other threads:[~2009-02-04 1:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 22:38 [PATCH] trivial: fix where cgroup documentation is not correctly referred to Thadeu Lima de Souza Cascardo
2009-02-03 2:12 ` KAMEZAWA Hiroyuki
2009-02-03 5:53 ` Li Zefan
2009-02-03 13:04 ` Thadeu Lima de Souza Cascardo
2009-02-03 17:08 ` Randy Dunlap
2009-02-03 20:48 ` Thadeu Lima de Souza Cascardo
2009-02-04 1:09 ` Li Zefan [this message]
2009-02-04 7:38 ` Paul Menage
2009-02-04 9:12 ` Jiri Kosina
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=4988EADB.4050508@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=cascardo@holoscopio.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=trivial@kernel.org \
/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.