All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peter Schiffer <pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [patch] set_mempolicy.2: wfix
Date: Wed, 23 Apr 2014 14:40:18 +0200	[thread overview]
Message-ID: <5357B4B2.3060401@gmail.com> (raw)
In-Reply-To: <5357AAF3.2010200-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 04/23/2014 01:58 PM, Peter Schiffer wrote:
> Hi Michael,
> 
> sending minor wording fix for set_mempolicy(2) man page.

Thanks, Peter. Applied. (But, I prefer inline patches.)

Cheers,

Michael

diff --git a/man2/set_mempolicy.2 b/man2/set_mempolicy.2
index f891cc4..843208c 100644
--- a/man2/set_mempolicy.2
+++ b/man2/set_mempolicy.2
@@ -99,7 +99,7 @@ are:
 A nonempty
 .I nodemask
 specifies physical node ids.
-Linux does will not remap the
+Linux will not remap the
 .I nodemask
 when the process moves to a different cpuset context,
 nor when the set of nodes allowed by the process's

-- 
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

      parent reply	other threads:[~2014-04-23 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 11:58 [patch] set_mempolicy.2: wfix Peter Schiffer
     [not found] ` <5357AAF3.2010200-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-04-23 12:40   ` Michael Kerrisk (man-pages) [this message]

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=5357B4B2.3060401@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pschiffe-H+wXaHxf7aLQT0dZR+AlfA@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 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.