public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Shuah Khan <shuahkh@osg.samsung.com>,
	linux-api@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Davidlohr Bueso <dave@stgolabs.net>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [PATCH 5/5] kselftest: Add exit code defines
Date: Fri, 27 Mar 2015 16:09:23 -0700	[thread overview]
Message-ID: <5515E323.1070800@linux.intel.com> (raw)
In-Reply-To: <1427497178.3986.1.camel@ellerman.id.au>



On 3/27/15 3:59 PM, Michael Ellerman wrote:
> On Fri, 2015-03-27 at 15:17 -0700, Darren Hart wrote:
>> Define the exit codes with KSFT_PASS and similar so tests can use these
>> directly if they choose. Also enable harnesses and other tooling to use
>> the defines instead of hardcoding the return codes.
>  
> +1
> 
>> diff --git a/tools/testing/selftests/kselftest.h b/tools/testing/selftests/kselftest.h
>> index 572c888..ef1c80d 100644
>> --- a/tools/testing/selftests/kselftest.h
>> +++ b/tools/testing/selftests/kselftest.h
>> @@ -13,6 +13,13 @@
>>  #include <stdlib.h>
>>  #include <unistd.h>
>>  
>> +/* define kselftest exit codes */
>> +#define KSFT_PASS  0
>> +#define KSFT_FAIL  1
>> +#define KSFT_XFAIL 2
>> +#define KSFT_XPASS 3
>> +#define KSFT_SKIP  4
>> +
>>  /* counters */
>>  struct ksft_count {
>>  	unsigned int ksft_pass;
>> @@ -40,23 +47,23 @@ static inline void ksft_print_cnts(void)
>>  
>>  static inline int ksft_exit_pass(void)
>>  {
>> -	exit(0);
>> +	exit(KSFT_PASS);
>>  }
> 
> Am I the only person who's bothered by the fact that these don't actually
> return int?

That bothered me to, but I couldn't be bothered to go read the manuals
apparently to come up with a compelling argument :-)

I also think the ksft_exit* routines should go ahead and increment the
counters (at least optionally) so we don't have to call two functions.

-- 
Darren Hart
Intel Open Source Technology Center

  reply	other threads:[~2015-03-27 23:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 22:17 [GIT PULL] selftest: Add futex functional tests Darren Hart
2015-03-27 22:17 ` [PATCH 1/5] selftests: " Darren Hart
2015-05-06 17:28   ` Shuah Khan
2015-05-06 18:04     ` Darren Hart
2015-03-27 22:17 ` [PATCH 2/5] selftest/futex: Update Makefile to use lib.mk Darren Hart
2015-03-29 23:49   ` Michael Ellerman
2015-03-30 16:31     ` Darren Hart
2015-03-31 23:28       ` Michael Ellerman
2015-03-27 22:17 ` [PATCH 3/5] selftest/futex: Increment ksft pass and fail counters Darren Hart
2015-03-27 22:17 ` [PATCH 4/5] selftest: Add futex tests to the top-level Makefile Darren Hart
2015-03-27 22:17 ` [PATCH 5/5] kselftest: Add exit code defines Darren Hart
2015-03-27 22:59   ` Michael Ellerman
2015-03-27 23:09     ` Darren Hart [this message]
2015-03-29 23:44       ` Michael Ellerman
2015-03-30 16:26         ` Darren Hart
2015-03-30 16:30           ` Peter Zijlstra
     [not found] ` <551ABE00.9050003@osg.samsung.com>
2015-03-31 16:24   ` [GIT PULL] selftest: Add futex functional tests Darren Hart
2015-03-31 16:37     ` Shuah Khan
2015-04-08  4:12       ` Darren Hart
2015-04-09  5:41         ` Shuah Khan
2015-04-09  5:44           ` Darren Hart
2015-05-06 18:34 ` Davidlohr Bueso
  -- strict thread matches above, loose matches on Subject: below --
2015-05-08 22:09 [PATCH 1/5] selftests: " Darren Hart
2015-05-08 22:09 ` [GIT PULL v2] selftest: " Darren Hart
2015-05-08 22:09   ` [PATCH 5/5] kselftest: Add exit code defines Darren Hart

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=5515E323.1070800@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=dave@stgolabs.net \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mpe@ellerman.id.au \
    --cc=peterz@infradead.org \
    --cc=shuahkh@osg.samsung.com \
    --cc=tglx@linutronix.de \
    /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