From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 1/2] pkeys.7: wfix
Date: Tue, 11 Jan 2022 19:31:13 +0100 [thread overview]
Message-ID: <160f7e9a-9d24-6cc7-fb9f-04527da0ca79@gmail.com> (raw)
In-Reply-To: <cca0611edc27083e28da425ca6082e0c31ba6064.1641925582.git.nabijaczleweli@nabijaczleweli.xyz>
On 1/11/22 19:27, наб wrote:
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Patch applied.
Thanks!
Alex
> ---
> man7/pkeys.7 | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/man7/pkeys.7 b/man7/pkeys.7
> index 73ddcdc43..9c2356f65 100644
> --- a/man7/pkeys.7
> +++ b/man7/pkeys.7
> @@ -42,8 +42,9 @@ to change the contents of a register in order to remove write
> access, or all access to a tagged page.
> .PP
> Protection keys work in conjunction with the existing
> -.BR PROT_READ /
> -.BR PROT_WRITE /
> +.BR PROT_READ ,
> +.BR PROT_WRITE ,
> +and
> .BR PROT_EXEC
> permissions passed to system calls such as
> .BR mprotect (2)
--
Alejandro Colomar
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2022-01-11 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 16:21 [PATCH] pkeys.7: ffix наб
2022-01-10 18:13 ` Alejandro Colomar (man-pages)
2022-01-10 18:49 ` наб
2022-01-11 18:17 ` Alejandro Colomar (man-pages)
2022-01-11 18:27 ` [PATCH v2 1/2] pkeys.7: wfix наб
2022-01-11 18:31 ` Alejandro Colomar (man-pages) [this message]
2022-01-11 18:28 ` [PATCH v2 2/2] glob.3: srcfix наб
2022-01-11 18:47 ` Alejandro Colomar (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=160f7e9a-9d24-6cc7-fb9f-04527da0ca79@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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.