From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: fam@euphon.net, berrange@redhat.com, stefanb@linux.vnet.ibm.com,
richard.henderson@linaro.org, f4bug@amsat.org, cota@braap.org,
stefanha@redhat.com, pbonzini@redhat.com,
marcandre.lureau@redhat.com, aurelien@aurel32.net
Subject: Re: [PATCH v1 2/5] tests/rcutorture: update usage hint
Date: Wed, 12 Feb 2020 21:46:26 +0100 [thread overview]
Message-ID: <0bf5f39b-14ea-8dc0-c787-d92fdc944448@redhat.com> (raw)
In-Reply-To: <20200207113939.9247-3-alex.bennee@linaro.org>
On 2/7/20 12:39 PM, Alex Bennée wrote:
> Although documented in the comments we don't display all the various
> invocations we can in the usage.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> tests/rcutorture.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/rcutorture.c b/tests/rcutorture.c
> index 49311c82ea4..e8b2169e7dd 100644
> --- a/tests/rcutorture.c
> +++ b/tests/rcutorture.c
> @@ -413,7 +413,8 @@ static void gtest_stress_10_5(void)
>
> static void usage(int argc, char *argv[])
> {
> - fprintf(stderr, "Usage: %s [nreaders [ perf | stress ] ]\n", argv[0]);
> + fprintf(stderr, "Usage: %s [nreaders [ [r|u]perf | stress [duration]]\n",
> + argv[0]);
> exit(-1);
> }
>
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-02-12 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 11:39 [PATCH v1 0/5] testing/next (rcutorture and misc tweaks) Alex Bennée
2020-02-07 11:39 ` [PATCH v1 1/5] tests/tcg: include a skip runner for pauth3 with plugins Alex Bennée
2020-02-07 11:39 ` [PATCH v1 2/5] tests/rcutorture: update usage hint Alex Bennée
2020-02-12 20:46 ` Philippe Mathieu-Daudé [this message]
2020-02-07 11:39 ` [PATCH v1 3/5] tests/rcutorture: better document locking of stats Alex Bennée
2020-02-12 20:47 ` Philippe Mathieu-Daudé
2020-02-07 11:39 ` [PATCH v1 4/5] tests/rcutorture: mild documenting refactor of update thread Alex Bennée
2020-02-07 11:39 ` [PATCH v1 5/5] travis.yml: Test the s390-ccw build, too Alex Bennée
2020-02-12 20:48 ` Philippe Mathieu-Daudé
2020-02-13 8:34 ` Cornelia Huck
2020-02-12 19:42 ` [PATCH v1 0/5] testing/next (rcutorture and misc tweaks) Alex Bennée
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=0bf5f39b-14ea-8dc0-c787-d92fdc944448@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=stefanha@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).