From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: mtk.manpages@gmail.com,
Piotr Kwapulinski <kwapulinski.piotr@gmail.com>,
mhocko@kernel.org, mgorman@techsingularity.net,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rik van Riel <riel@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-man <linux-man@vger.kernel.org>,
Brice Goglin <Brice.Goglin@inria.fr>
Subject: Re: Rewording language in mbind(2) to "threads" not "processes"
Date: Sat, 22 Oct 2016 12:08:59 +0200 [thread overview]
Message-ID: <f1390356-5b8a-9b8f-e426-ad820b484af1@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1610210844120.24973@east.gentwo.org>
On 10/21/2016 03:44 PM, Christoph Lameter wrote:
> On Fri, 21 Oct 2016, Michael Kerrisk (man-pages) wrote:
>
>> Did you have any thoughts on my follow-on question below?
>
> There was only one AFAICT?
>
>>> Thanks. So, are all the other cases where I changed "process" to
>>> "thread" okay then?
>
>>From what I see yes.
>
>
Thanks, Christoph. I've added a Reviewed-by from you.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-10-22 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 8:38 Michael Kerrisk (man-pages)
2016-10-13 18:16 ` Christoph Lameter
2016-10-14 10:09 ` Michael Kerrisk (man-pages)
2016-10-21 7:22 ` Michael Kerrisk (man-pages)
2016-10-21 13:44 ` Christoph Lameter
2016-10-22 10:08 ` Michael Kerrisk (man-pages) [this message]
2016-10-22 10:08 ` Michael Kerrisk (man-pages)
2016-10-25 15:40 ` Piotr Kwapulinski
2016-10-31 11:59 ` 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=f1390356-5b8a-9b8f-e426-ad820b484af1@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=Brice.Goglin@inria.fr \
--cc=a.p.zijlstra@chello.nl \
--cc=cl@linux.com \
--cc=kwapulinski.piotr@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=riel@redhat.com \
/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