From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 1/1] fhandler_process.cc(format_process_stat): fix /proc/pid/stat issues
Date: Wed, 11 May 2022 10:03:04 +0200 [thread overview]
Message-ID: <YnttuBkTc0HN3KQh@calimero.vinschen.de> (raw)
In-Reply-To: <20220510144443.5555-2-Brian.Inglis@SystematicSW.ab.ca>
On May 10 08:44, Brian Inglis wrote:
>
> fix tty_nr maj/min bits, vmmaxrss units, and x86 format mismatch:
> ctty maj is 31:16, min is 15:0; tty_nr s/b maj 15:8, min 31:20, 7:0;
> vmmaxrss s/b bytes not pages;
> times all 64 bit - change formats of first two instances from %lu to %U;
> realign sprintf formats and variables/values in more logical groups
> ---
> winsup/cygwin/fhandler_process.cc | 33 +++++++++++++++++++------------
> 1 file changed, 20 insertions(+), 13 deletions(-)
>
Pushed.
Thanks,
Corinna
next prev parent reply other threads:[~2022-05-11 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 14:44 [PATCH 0/1] " Brian Inglis
2022-05-10 14:44 ` [PATCH 1/1] " Brian Inglis
2022-05-11 8:03 ` Corinna Vinschen [this message]
2022-05-11 14:55 ` [PATCH 0/1] " Mohammad HOQUE
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=YnttuBkTc0HN3KQh@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).