From: Alejandro Colomar <alx@kernel.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 3/6] proc_pid_io.5: wfix
Date: Thu, 14 Mar 2024 17:22:19 +0100 [thread overview]
Message-ID: <ZfMkO8VeD63b-ucQ@debian> (raw)
In-Reply-To: <b59362221695a6671c767e9b3adf4e671193acb2.1710339990.git.nabijaczleweli@nabijaczleweli.xyz>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On Wed, Mar 13, 2024 at 03:26:48PM +0100, наб wrote:
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Patch applied. Thanks.
Cheers,
Alex
> ---
> man5/proc_pid_io.5 | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/man5/proc_pid_io.5 b/man5/proc_pid_io.5
> index f66d8c635..4d97bd95f 100644
> --- a/man5/proc_pid_io.5
> +++ b/man5/proc_pid_io.5
> @@ -88,9 +88,9 @@ .SH DESCRIPTION
> while process B is updating one of these 64-bit counters,
> process A could see an intermediate result.
> .IP
> -Permission to access this file is governed by a ptrace access mode
> -.B PTRACE_MODE_READ_FSCREDS
> -check; see
> -.BR ptrace (2).
> +Permission to access this file is governed by
> +.BR ptrace (2)
> +access mode
> +.BR PTRACE_MODE_READ_FSCREDS .
> .SH SEE ALSO
> .BR proc (5)
> --
> 2.39.2
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-14 16:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 14:26 [PATCH 1/6] proc_pid_io.5: stats include children наб
2024-03-13 14:26 ` [PATCH 2/6] proc_pid_io.5: dewafflify наб
2024-03-14 16:21 ` Alejandro Colomar
2024-03-13 14:26 ` [PATCH 3/6] proc_pid_io.5: wfix наб
2024-03-14 16:22 ` Alejandro Colomar [this message]
2024-03-13 14:26 ` [PATCH 4/6] proc_pid_io.5: mention atomicity in atomicity note наб
2024-03-14 16:28 ` Alejandro Colomar
2024-03-13 14:26 ` [PATCH 5/6] getrusage.2: proc(5) /proc/pid/stat -> proc_pid_stat(5) наб
2024-03-14 16:31 ` Alejandro Colomar
2024-03-13 14:26 ` [PATCH 6/6] getrusage.2, proc_pid_io.5: crosslink наб
2024-03-14 16:33 ` Alejandro Colomar
2024-03-14 16:19 ` [PATCH 1/6] proc_pid_io.5: stats include children Alejandro Colomar
2024-03-17 11:01 ` [PATCH v2 2/2] proc_pid_io.5: dewafflify наб
2024-03-17 12:15 ` Alejandro Colomar
2024-03-17 13:31 ` [PATCH v3] " наб
2024-03-17 14:12 ` Alejandro Colomar
2024-03-17 15:37 ` [PATCH v4] " наб
2024-03-17 16:08 ` Alejandro Colomar
2024-03-17 11:01 ` [PATCH v2 1/2] proc_pid_io.5: stats include children наб
2024-03-17 11:39 ` Alejandro Colomar
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=ZfMkO8VeD63b-ucQ@debian \
--to=alx@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox