From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] prctl.2: tfix
Date: Mon, 20 Jul 2020 11:27:01 +0200 [thread overview]
Message-ID: <52be2b74-db63-d9a6-0c69-1f972cd0f3a9@gmail.com> (raw)
In-Reply-To: <20200720054938.4312-1-jwilk@jwilk.net>
On 7/20/20 7:49 AM, Jakub Wilk wrote:
> Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
Thanks, Jakub. Patch applied.
Cheers,
Michael
> ---
> man2/prctl.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/prctl.2 b/man2/prctl.2
> index d2a52d34c..7658b32ce 100644
> --- a/man2/prctl.2
> +++ b/man2/prctl.2
> @@ -1082,7 +1082,7 @@ otherwise, this value is preserved across
> The parent-death signal setting is also cleared upon changes to
> any of the following thread credentials:
> .\" FIXME capability changes can also trigger this; see
> -.\" kernel/cred.c::commit_creds inthe Linux 5.6 source.
> +.\" kernel/cred.c::commit_creds in the Linux 5.6 source.
> effective user ID, effective group ID, filesystem user ID,
> or filesystem group ID.
> .\" prctl PR_GET_PDEATHSIG
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-07-20 9:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 5:49 [PATCH] prctl.2: tfix Jakub Wilk
2020-07-20 9:27 ` Michael Kerrisk (man-pages) [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 4:05 Eric Biggers
2023-07-15 16:40 ` Alejandro Colomar
2022-10-11 6:25 Jakub Wilk
2022-10-11 20:53 ` Alejandro Colomar
2023-03-31 22:58 ` Alejandro Colomar
2020-05-25 13:21 Jakub Wilk
2020-05-25 13:24 ` Michael Kerrisk (man-pages)
2020-04-22 9:59 Jakub Wilk
2020-04-22 11:22 ` 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=52be2b74-db63-d9a6-0c69-1f972cd0f3a9@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.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).