On Thu, 12 Jan 2017 14:24:27 -0800
"W. Trevor King" <wk...@tremily.us> wrote:

> This looks like it was accidentally caught up in e21a05cb (doc:
> cpuset: Update the cpuset flag file, 2010-02-24).
> While I'm touching the line, also fix the posessive "cpusets" ->
> "cpuset's".
> Signed-off-by: W. Trevor King <wk...@tremily.us>
> ---
>  Documentation/cgroup-v1/cpusets.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> This patch is based on v4.9, but the lines I'm touching don't churn
> much so it should apply to any recent version.
> diff --git a/Documentation/cgroup-v1/cpusets.txt 
> b/Documentation/cgroup-v1/cpusets.txt
> index e5ac5da86..8402dd6 100644
> --- a/Documentation/cgroup-v1/cpusets.txt
> +++ b/Documentation/cgroup-v1/cpusets.txt
> @@ -615,7 +615,7 @@ to allocate a page of memory for that task.
>  If a cpuset has its 'cpuset.cpus' modified, then each task in that cpuset
>  will have its allowed CPU placement changed immediately.  Similarly,
> -if a task's pid is written to another cpusets 'cpuset.tasks' file, then its
> +if a task's pid is written to another cpuset's 'tasks' file, then its

So I'll confess that I don't understand this change.  All of the control
files are referred to as cpuset.whatever in this document; why should
this one, in particular, be different?


To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to