linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 5/6] getrusage.2: proc(5) /proc/pid/stat -> proc_pid_stat(5)
Date: Thu, 14 Mar 2024 17:31:56 +0100	[thread overview]
Message-ID: <ZfMmfTx-R-Ac78-g@debian> (raw)
In-Reply-To: <e48a7ec4150f9b2930c4b8bbc53f66f55da77b75.1710339990.git.nabijaczleweli@nabijaczleweli.xyz>

[-- Attachment #1: Type: text/plain, Size: 996 bytes --]

Hi!

On Wed, Mar 13, 2024 at 03:26:52PM +0100, наб wrote:
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>

I've also added
  Fixes: bbc21bc4dbef ("proc.5, proc_pid_stat.5: Split /proc/PID/stat from proc(5)")

Patch applied.  Thanks!


Cheers,
Alex

> ---
>  man2/getrusage.2 | 8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
> 
> diff --git a/man2/getrusage.2 b/man2/getrusage.2
> index 8323bef35..8baff09c4 100644
> --- a/man2/getrusage.2
> +++ b/man2/getrusage.2
> @@ -239,15 +239,11 @@ .SH HISTORY
>  .SH NOTES
>  Resource usage metrics are preserved across an
>  .BR execve (2).
> -.P
> -See also the description of
> -.IR /proc/ pid /stat
> -in
> -.BR proc (5).
>  .SH SEE ALSO
>  .BR clock_gettime (2),
>  .BR getrlimit (2),
>  .BR times (2),
>  .BR wait (2),
>  .BR wait4 (2),
> -.BR clock (3)
> +.BR clock (3),
> +.BR proc_pid_stat (5)
> -- 
> 2.39.2
> 



-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-03-14 16:31 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
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 [this message]
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=ZfMmfTx-R-Ac78-g@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;
as well as URLs for NNTP newsgroup(s).