From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: linux-rt-users@vger.kernel.org, williams@redhat.com, jkacur@redhat.com
Subject: Re: [PATCH 2/3] don't use exit(-1) for failures
Date: Thu, 14 Apr 2016 08:53:36 +0200 [thread overview]
Message-ID: <20160414065336.GH10108@pengutronix.de> (raw)
In-Reply-To: <1458239345-30892-3-git-send-email-lcapitulino@redhat.com>
Hallo,
On Thu, Mar 17, 2016 at 02:29:04PM -0400, Luiz Capitulino wrote:
> The kernel uses only 8 bits of the status as a return
> code, so this actually becomes 255 in the shell.
>
> In any case, the most widely convension is exit(1)
> for failures, so let's be consistent.
The more portable version for this is to use EXIT_FAILURE. Not sure
though if it matters even for software that is not linux-centric like
rt-tests.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-04-14 6:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 18:29 [PATCH v2 0/3] rt-tests: minor fixes Luiz Capitulino
2016-03-17 18:29 ` [PATCH 1/3] rt-migrate-test: fix return code Luiz Capitulino
2016-03-22 14:22 ` John Kacur
2016-03-22 14:47 ` Luiz Capitulino
2016-03-22 14:59 ` John Kacur
2016-03-22 15:30 ` Luiz Capitulino
2016-03-22 16:24 ` John Kacur
2016-03-22 16:43 ` Luiz Capitulino
2016-03-22 15:05 ` John Kacur
2016-03-17 18:29 ` [PATCH 2/3] don't use exit(-1) for failures Luiz Capitulino
2016-03-22 14:21 ` John Kacur
2016-03-22 14:30 ` Luiz Capitulino
2016-04-14 6:53 ` Uwe Kleine-König [this message]
2016-03-17 18:29 ` [PATCH 3/3] cyclictest: initialize 'stop' early Luiz Capitulino
2016-03-22 14:55 ` John Kacur
2016-03-22 14:59 ` Luiz Capitulino
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=20160414065336.GH10108@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=jkacur@redhat.com \
--cc=lcapitulino@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;
as well as URLs for NNTP newsgroup(s).