From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Yuri Kozlov <yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] cpuset.7: tfix
Date: Sat, 21 Jun 2014 07:54:29 +0200 [thread overview]
Message-ID: <53A51E15.6000708@gmail.com> (raw)
In-Reply-To: <1403327761-4115-1-git-send-email-yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org>
Thanks, Yuri. Applied.
Cheers,
Michael
On 06/21/2014 07:16 AM, Yuri Kozlov wrote:
> ---
> man7/cpuset.7 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man7/cpuset.7 b/man7/cpuset.7
> index 3c74dac..1b89d79 100644
> --- a/man7/cpuset.7
> +++ b/man7/cpuset.7
> @@ -247,7 +247,7 @@ format of
> Flag (0 or 1).
> If set (1), the cpuset has exclusive use of
> its memory nodes (no sibling or cousin may overlap).
> -Also if set (1), the cpuset is a \fBHardwall\fR cpuset (see below.)
> +Also if set (1), the cpuset is a \fBHardwall\fR cpuset (see below).
> By default this is off (0).
> Newly created cpusets also initially default this to off (0).
>
> @@ -261,7 +261,7 @@ of that cpuset's parent cpuset.
> .TP
> .IR cpuset.mem_hardwall " (since Linux 2.6.26)"
> Flag (0 or 1).
> -If set (1), the cpuset is a \fBHardwall\fR cpuset (see below.)
> +If set (1), the cpuset is a \fBHardwall\fR cpuset (see below).
> Unlike \fBmem_exclusive\fR,
> there is no constraint on whether cpusets
> marked \fBmem_hardwall\fR may have overlapping
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-21 5:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-21 5:16 [PATCH] cpuset.7: tfix Yuri Kozlov
[not found] ` <1403327761-4115-1-git-send-email-yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org>
2014-06-21 5:54 ` Michael Kerrisk (man-pages) [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-17 2:55 David Turner
[not found] ` <1471402525-21666-1-git-send-email-novalis-qEvXGNtQsBNAfugRpC6u6w@public.gmane.org>
2016-08-17 5:07 ` Michael Kerrisk (man-pages)
2014-06-18 17:01 Yuri Kozlov
[not found] ` <1403110903-4197-1-git-send-email-yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org>
2014-06-18 19:15 ` Michael Kerrisk (man-pages)
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=53A51E15.6000708@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).