The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Shuah Khan <shuah@kernel.org>
To: John Stultz <john.stultz@linaro.org>,
	Shuah Khan <shuahkh@osg.samsung.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Stephen Boyd <sboyd@codeaurora.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 0/3] selfttests: timers ksft_ stubs handling changes
Date: Thu, 10 Aug 2017 18:51:11 -0600	[thread overview]
Message-ID: <bc7ff151-42e0-ca94-1d85-69df798dce57@kernel.org> (raw)
In-Reply-To: <CALAqxLWJfBZ3oEowHiAvcfy1fNqOnm80mrUv3HnyTxPbmL8Z7Q@mail.gmail.com>

On 08/10/2017 06:10 PM, John Stultz wrote:
> On Thu, Aug 10, 2017 at 4:53 PM, Shuah Khan <shuahkh@osg.samsung.com> wrote:
>> This patch series consists of changes to:
>>
>> Move ksft_ stubs from individual tests into kselftest_stubs.h and change
>> tests to include it.
>>
>> Fix posix_timers and freq-step tests to run without ksft_ framework.
>>
>> This is in preparation to convert timers tests to ksft TAP 13 format.
>>
>> Question for John Stultz:
>>
>> The conversion work will be easier without the requirement to be able to
>> build and run these tests without ksft_ framework. So far the stubs are
>> simpler. It is might be necessary to ifdef some code paths to have sane
>> output for both KTEST and !KTEST cases.
>>
>> Would it be easier to pull in kselftest.h into timers external repo
>> (if one still exists). This is based on the observation that newer
>> timer tests don't support !KTEST case e.g: posix_timers and freq-step.
>>
>> Please review and let me know how you would like me to proceed with the
>> conversion. I am looking for answer to how important is it to continue to
>> support !KTEST case.
> 
> Yea. I'm thinking at this point I'm fine with dropping the attempt to
> keep kselftest and my external timekeeping tests in sync.

Would you like me to clean !KTEST support or leave it the way it is.
It sounds like, I will drop these patches anyway.

> 
> Though something that might be nice however is having some place that
> keeps tarball releases of kselftest around? As it would make pulling
> tests onto a target machine a bit easier. Does that already exist?
> 

There is an install script tools/testing/selftests/gen_kselftest_tar.sh
for generating tar-ball for compiled tests at the moment. There is none
for source package.

thanks,
-- Shuah

  reply	other threads:[~2017-08-11  0:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 23:53 [PATCH 0/3] selfttests: timers ksft_ stubs handling changes Shuah Khan
2017-08-10 23:53 ` [PATCH 1/3] selftests: timers: move ksft_ stubs from tests into kselftest_stubs.h Shuah Khan
2017-08-10 23:53 ` [PATCH 2/3] selftests: timers: posix_timers: fix to work without ksft framework Shuah Khan
2017-08-10 23:53 ` [PATCH 3/3] selftests: timers: freq-step: " Shuah Khan
2017-08-11  0:10 ` [PATCH 0/3] selfttests: timers ksft_ stubs handling changes John Stultz
2017-08-11  0:51   ` Shuah Khan [this message]
2017-08-11  0:57     ` John Stultz

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=bc7ff151-42e0-ca94-1d85-69df798dce57@kernel.org \
    --to=shuah@kernel.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=sboyd@codeaurora.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