From: Clark Williams <williams@redhat.com>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: John Kacur <jkacur@redhat.com>, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH 1/1] cyclictest: Fix long priority help text option
Date: Wed, 22 Jul 2015 10:21:27 -0500 [thread overview]
Message-ID: <20150722102127.12ee911e@sluggy> (raw)
In-Reply-To: <1437569099-2965-1-git-send-email-alexander.stein@systec-electronic.com>
On Wed, 22 Jul 2015 14:44:59 +0200
Alexander Stein <alexander.stein@systec-electronic.com> wrote:
> The help text shows prio as the long option name for the process priority.
> But it is actually priority.
>
> Signed-off-by: Alexander Stein <alexander.stein@systec-electronic.com>
> ---
> src/cyclictest/cyclictest.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/cyclictest/cyclictest.c b/src/cyclictest/cyclictest.c
> index 34053c5..c178a74 100644
> --- a/src/cyclictest/cyclictest.c
> +++ b/src/cyclictest/cyclictest.c
> @@ -1062,7 +1062,7 @@ static void display_help(int error)
> "-N --nsecs print results in ns instead of us (default us)\n"
> "-o RED --oscope=RED oscilloscope mode, reduce verbose output by RED\n"
> "-O TOPT --traceopt=TOPT trace option\n"
> - "-p PRIO --prio=PRIO priority of highest prio thread\n"
> + "-p PRIO --priority=PRIO priority of highest prio thread\n"
> "-P --preemptoff Preempt off tracing (used with -b)\n"
> "-q --quiet print only a summary on exit\n"
> " --priospread spread priority levels starting at specified value\n"
> --
> 2.3.6
Thanks, I've pulled this into my tree for the next release.
Clark
next prev parent reply other threads:[~2015-07-22 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 12:44 [PATCH 1/1] cyclictest: Fix long priority help text option Alexander Stein
2015-07-22 15:21 ` Clark Williams [this message]
2015-07-24 13:14 ` 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=20150722102127.12ee911e@sluggy \
--to=williams@redhat.com \
--cc=alexander.stein@systec-electronic.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