The patch titled
Subject: cgroups: documentation: fix wrong cgroupfs paths
has been removed from the -mm tree. Its filename was
cgroups-documentation-fix-wrong-cgroupfs-paths.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: SeongJae Park <sj38.park@xxxxxxxxx>
Subject: cgroups: documentation: fix wrong cgroupfs paths
Few paths used as example to describe cgroupfs usage have been wrong from
f6e07d38078e ("Documentation: update cgroupfs mount point") by mistake.
This patch fixes those trivial wrong paths.
Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
Cc: Jonathan Corbet <corbet@xxxxxxx>
Cc: Tejun Heo <tj@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/cgroups/cgroups.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN Documentation/cgroups/cgroups.txt~cgroups-documentation-fix-wrong-cgroupfs-paths Documentation/cgroups/cgroups.txt
--- a/Documentation/cgroups/cgroups.txt~cgroups-documentation-fix-wrong-cgroupfs-paths
+++ a/Documentation/cgroups/cgroups.txt
@@ -312,10 +312,10 @@ the "cpuset" cgroup subsystem, the steps
2) mkdir /sys/fs/cgroup/cpuset
3) mount -t cgroup -ocpuset cpuset /sys/fs/cgroup/cpuset
4) Create the new cgroup by doing mkdir's and write's (or echo's) in
- the /sys/fs/cgroup virtual file system.
+ the /sys/fs/cgroup/cpuset virtual file system.
5) Start a task that will be the "founding father" of the new job.
6) Attach that task to the new cgroup by writing its PID to the
- /sys/fs/cgroup/cpuset/tasks file for that cgroup.
+ /sys/fs/cgroup/cpuset tasks file for that cgroup.
7) fork, exec or clone the job tasks from this founding father task.
For example, the following sequence of commands will setup a cgroup
_
Patches currently in -mm which might be from sj38.park@xxxxxxxxx are
linux-next.patch
cgroups-documentation-fix-trivial-typos-and-wrong-paragraph-numberings.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
