From: Tomas Glozar <tglozar@redhat.com>
To: John Kacur <jkacur@redhat.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
Tomas Glozar <tglozar@redhat.com>
Subject: [PATCH] rt-tests: cyclictest: Fix -A long name in manpage
Date: Thu, 26 Feb 2026 14:18:28 +0100 [thread overview]
Message-ID: <20260226131828.234378-1-tglozar@redhat.com> (raw)
The cyclictest manpage gives the long name for -A option as --align,
however, the proper name in both help message and getopt_long() is
--aligned.
Use the correct name in the manpage.
Signed-off-by: Tomas Glozar <tglozar@redhat.com>
---
src/cyclictest/cyclictest.8 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/cyclictest/cyclictest.8 b/src/cyclictest/cyclictest.8
index 6becd19..ff2cb96 100644
--- a/src/cyclictest/cyclictest.8
+++ b/src/cyclictest/cyclictest.8
@@ -17,7 +17,7 @@
cyclictest \- High resolution test program
.SH SYNOPSIS
.SY cyclictest
-.RI "[ \-hfmnqrsvMS ] [\-a " proc " ] [\-A " align " ] [\-b " usec " ] [\-c " clock " ] [\-d " dist " ] \
+.RI "[ \-hfmnqrsvMS ] [\-a " proc " ] [\-A " aligned " ] [\-b " usec " ] [\-c " clock " ] [\-d " dist " ] \
[\-h " histogram " ] [\-i " intv " ] [\-\-json " filename " ] [\-l " loop " ] [\-o " red " ] \
[\-p " prio " ] [\-t " num " ] [\-D " time "] [\-w] [\-W] [\-y " policy " ] [ \-S | \-U ]"
@@ -47,7 +47,7 @@ field in /proc/cpuinfo. See numa(3) for more information on specifying CPU sets
* Support for CPU sets requires libnuma version >= 2. For libnuma v1, PROC-SET,
if specified, must be a single CPU number.
.TP
-.B \-A, \-\-align=USEC
+.B \-A, \-\-aligned=USEC
Align thread wakeups to a specific offset in microseconds
.TP
.B \-b, \-\-breaktrace=USEC
--
2.53.0
next reply other threads:[~2026-02-26 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 13:18 Tomas Glozar [this message]
2026-02-26 19:43 ` [PATCH] rt-tests: cyclictest: Fix -A long name in manpage John Kacur
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=20260226131828.234378-1-tglozar@redhat.com \
--to=tglozar@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@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