From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Christian Brauner <christian@brauner.io>
Cc: mtk.manpages@gmail.com, adrian@lisas.de,
akpm@linux-foundation.org, arnd@arndb.de, avagin@gmail.com,
christian.brauner@ubuntu.com, dhowells@redhat.com,
fweimer@redhat.com, jannh@google.com, keescook@chromium.org,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-man@vger.kernel.org, mingo@elte.hu, oleg@redhat.com,
xemul@virtuozzo.com
Subject: Re: [PATCH] clone.2: Fix typo
Date: Thu, 21 Nov 2019 12:25:48 +0100 [thread overview]
Message-ID: <9218d76c-96ec-920c-7304-a9247fb6d05a@gmail.com> (raw)
In-Reply-To: <20191121110646.1398-1-christian@brauner.io>
Hi Christian,
On 11/21/19 12:06 PM, Christian Brauner wrote:
> From: Christian Brauner <christian.brauner@ubuntu.com>
>
> This surely meant to say clone3() and not clone(3).
Thanks. Patch applied.
Cheers,
Michael
> Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
> ---
> man2/clone.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/clone.2 b/man2/clone.2
> index 382f6b791..e5ab2a096 100644
> --- a/man2/clone.2
> +++ b/man2/clone.2
> @@ -252,7 +252,7 @@ argument supplied to
> lb lb lb
> l l l
> li li l.
> -clone() clone(3) Notes
> +clone() clone3() Notes
> \fIcl_args\fP field
> flags & ~0xff flags For most flags; details below
> parent_tid pidfd See CLONE_PIDFD
>
> base-commit: be479fdf027a3288e88d53dbe05ba76bf202776e
>
Hi Christian,,
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2019-11-21 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 11:06 [PATCH] clone.2: Fix typo Christian Brauner
2019-11-21 11:25 ` 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=9218d76c-96ec-920c-7304-a9247fb6d05a@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=adrian@lisas.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=avagin@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=christian@brauner.io \
--cc=dhowells@redhat.com \
--cc=fweimer@redhat.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=xemul@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).