From: Benno Schulenberg <bensberg@telfort.nl>
To: util-linux@vger.kernel.org
Cc: Christian Goeschel Ndjomouo <cgoesc2@wgu.edu>
Subject: [PATCH] waitpid: consistently write the abbreviation "PID" in all-uppercase
Date: Mon, 9 Mar 2026 12:15:44 +0100 [thread overview]
Message-ID: <20260309111544.4952-1-bensberg@telfort.nl> (raw)
Also, use %d instead of %u, as all other comparable messages use %d.
CC: Christian Goeschel Ndjomouo <cgoesc2@wgu.edu>
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
---
misc-utils/waitpid.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/misc-utils/waitpid.c b/misc-utils/waitpid.c
index 865b537e9..d77a41c5e 100644
--- a/misc-utils/waitpid.c
+++ b/misc-utils/waitpid.c
@@ -74,7 +74,7 @@ static inline int get_pidfd(const struct waitpid_control *ctl, struct process_in
if (pi->pidfd_ino) {
fd = ul_get_valid_pidfd(pi->pid, pi->pidfd_ino);
if (fd < 0 && ctl->verbose)
- warnx(_("pidfd inode %"PRIu64" not found for pid %d"),
+ warnx(_("pidfd inode %"PRIu64" not found for PID %d"),
pi->pidfd_ino, pi->pid);
} else {
fd = pidfd_open(pi->pid, 0);
@@ -94,7 +94,7 @@ static void open_pidfds_or_err(const struct waitpid_control *ctl, struct process
warnx(_("PID %d has exited, skipping"), pi->pid);
continue;
}
- err_nosys(EXIT_FAILURE, _("could not open pid %u"), pi->pid);
+ err_nosys(EXIT_FAILURE, _("could not open PID %d"), pi->pid);
}
}
}
--
2.53.0
next reply other threads:[~2026-03-09 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 11:15 Benno Schulenberg [this message]
2026-03-12 10:14 ` [PATCH] waitpid: consistently write the abbreviation "PID" in all-uppercase Karel Zak
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=20260309111544.4952-1-bensberg@telfort.nl \
--to=bensberg@telfort.nl \
--cc=cgoesc2@wgu.edu \
--cc=util-linux@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