From: John Kacur <jkacur@redhat.com>
To: "Uwe Kleine-König" <ukleinek@debian.org>
Cc: Clark Williams <williams@redhat.com>, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH rt-tests] cyclictest: fix typos
Date: Mon, 18 Nov 2019 20:24:18 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.21.1911182023570.30318@planxty> (raw)
In-Reply-To: <20191117214038.28094-1-ukleinek@debian.org>
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
On Sun, 17 Nov 2019, Uwe Kleine-König wrote:
> The called function is called clock_gettime with "only" two t as can be
> seen tree lines above. Also there was a wrong r in useful.
> ---
> src/cyclictest/cyclictest.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/cyclictest/cyclictest.c b/src/cyclictest/cyclictest.c
> index 6be0525822ca..bca028fedffd 100644
> --- a/src/cyclictest/cyclictest.c
> +++ b/src/cyclictest/cyclictest.c
> @@ -802,7 +802,7 @@ static void *timerthread(void *param)
> ret = clock_gettime(par->clock, &now);
> if (ret != 0) {
> if (ret != EINTR)
> - warn("clock_getttime() failed. errno: %d\n",
> + warn("clock_gettime() failed. errno: %d\n",
> errno);
> goto out;
> }
> @@ -964,7 +964,7 @@ static void display_help(int error)
> " but will not drain your battery so quickly\n"
> "-m --mlockall lock current and future memory allocations\n"
> "-M --refresh_on_max delay updating the screen until a new max\n"
> - " latency is hit. Userful for low bandwidth.\n"
> + " latency is hit. Useful for low bandwidth.\n"
> "-N --nsecs print results in ns instead of us (default us)\n"
> "-o RED --oscope=RED oscilloscope mode, reduce verbose output by RED\n"
> "-p PRIO --priority=PRIO priority of highest prio thread\n"
> --
> 2.24.0
>
>
Signed-off-by: John Kacur@redhat.com
next prev parent reply other threads:[~2019-11-18 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 21:40 [PATCH rt-tests] cyclictest: fix typos Uwe Kleine-König
2019-11-18 19:24 ` John Kacur [this message]
2019-11-18 19:26 ` 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=alpine.LFD.2.21.1911182023570.30318@planxty \
--to=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=ukleinek@debian.org \
--cc=williams@redhat.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 NNTP newsgroup(s).