From: John Kacur <jkacur@redhat.com>
To: David Sommerseth <davids@redhat.com>
Cc: linux-rt-users@vger.kernel.org, williams@redhat.com
Subject: Re: [PATCH 1/4] Fixed missing parsing of short arguments in classic_pi
Date: Tue, 22 Dec 2009 21:50:36 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0912222145010.8838@localhost.localdomain> (raw)
In-Reply-To: <1261496858-12744-2-git-send-email-davids@redhat.com>
On Tue, 22 Dec 2009, David Sommerseth wrote:
> Signed-off-by: David Sommerseth <davids@redhat.com>
> ---
> src/pi_tests/classic_pi.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/src/pi_tests/classic_pi.c b/src/pi_tests/classic_pi.c
> index 59e907b..2b8ef3d 100644
> --- a/src/pi_tests/classic_pi.c
> +++ b/src/pi_tests/classic_pi.c
> @@ -198,7 +198,7 @@ int main(int argc, char **argv)
> setvbuf (stdout, NULL, _IONBF, 0);
>
> /* process command line arguments */
> - while ((opt = getopt_long(argc, argv, "+", options, NULL)) != -1) {
> + while ((opt = getopt_long(argc, argv, "vqni:", options, NULL)) != -1) {
> switch (opt) {
> case '?':
> usage();
> --
> 1.6.2.5
David
Thanks - I fixed-up your patch to put back the leading '+' or else you
change the behaviour when a non-option is given between two real options.
We have been actively maintaining pi_stress, but classic_stress is a proof
of concept, so I don't know how much longer we want to maintain the code
here.
I pushed your patch with my modification to
git://git.kernel.org/pub/scm/linux/kernel/git/jkacur/rt-tests.git
branch: rt-tests-dev-new
Clark please pull above.
>From 2e2c1eb6ae2147ae68f1af4a0cc90066ad3c4bd0 Mon Sep 17 00:00:00 2001
From: David Sommerseth <davids@redhat.com>
Date: Tue, 22 Dec 2009 16:47:35 +0100
Subject: [PATCH] Fixed missing parsing of short arguments in classic_pi (David)
- Added the '+' back to the arguments (John)
Signed-off-by: David Sommerseth <davids@redhat.com>
Signed-off-by: John Kacur <jkacur@redhat.com>
---
src/pi_tests/classic_pi.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/pi_tests/classic_pi.c b/src/pi_tests/classic_pi.c
index 59e907b..91a8d6a 100644
--- a/src/pi_tests/classic_pi.c
+++ b/src/pi_tests/classic_pi.c
@@ -198,7 +198,7 @@ int main(int argc, char **argv)
setvbuf (stdout, NULL, _IONBF, 0);
/* process command line arguments */
- while ((opt = getopt_long(argc, argv, "+", options, NULL)) != -1) {
+ while ((opt = getopt_long(argc, argv, "+vqni:", options, NULL)) != -1) {
switch (opt) {
case '?':
usage();
--
1.6.0.6
next prev parent reply other threads:[~2009-12-22 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 15:47 [PATCH 0/4] Minor rt-tests updates David Sommerseth
2009-12-22 15:47 ` [PATCH 1/4] Fixed missing parsing of short arguments in classic_pi David Sommerseth
2009-12-22 20:50 ` John Kacur [this message]
2009-12-22 15:47 ` [PATCH 2/4] Missing parsing of --mlockall in signaltest David Sommerseth
2009-12-22 21:00 ` John Kacur
2009-12-22 15:47 ` [PATCH 3/4] Added --help screen info about -M / --refresh-on-max in cyclictest David Sommerseth
2009-12-22 21:02 ` John Kacur
2009-12-23 9:09 ` David Sommerseth
2009-12-22 21:59 ` John Kacur
2009-12-22 15:47 ` [PATCH 4/4] Updated man page to reflect --refresh-on-max agrument name change David Sommerseth
2009-12-22 22:00 ` 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.00.0912222145010.8838@localhost.localdomain \
--to=jkacur@redhat.com \
--cc=davids@redhat.com \
--cc=linux-rt-users@vger.kernel.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