From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
'Leonid Keller' <leonid-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
ofw_list <ofw-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>,
Yevgeny Kliteynik
<kliteyn-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
Regev Lev <regevl-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
Subject: [PATCH] infiniband-diags: -V, --version: exit with zero status
Date: Tue, 12 Jan 2010 11:22:46 +0200 [thread overview]
Message-ID: <20100112092246.GE26089@me> (raw)
In-Reply-To: <4DB33AEBD6F349EABE6AA1834AFBFC6B-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
When -V, --version command line option is used exit with zero status
after a version showing.
Signed-off-by: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
---
On 08:03 Tue 05 Jan , Sean Hefty wrote:
>
> Changes to the above components should be made to Sasha's tree first, or they
> risk being lost when I update the windows copy.
infiniband-diags/src/ibdiag_common.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/infiniband-diags/src/ibdiag_common.c b/infiniband-diags/src/ibdiag_common.c
index 735b898..99861f1 100644
--- a/infiniband-diags/src/ibdiag_common.c
+++ b/infiniband-diags/src/ibdiag_common.c
@@ -147,7 +147,7 @@ static int process_opt(int ch, char *optarg)
break;
case 'V':
fprintf(stderr, "%s %s\n", prog_name, get_build_version());
- exit(2);
+ exit(0);
case 'e':
madrpc_show_errors(1);
break;
--
1.6.6
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
parent reply other threads:[~2010-01-12 9:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4DB33AEBD6F349EABE6AA1834AFBFC6B-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>]
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=20100112092246.GE26089@me \
--to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=kliteyn-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
--cc=leonid-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ofw-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=regevl-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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