mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Shuah Khan <shuah.kh@samsung.com>,
	Tom Zanussi <tom.zanussi@linux.intel.com>,
	Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>,
	Oleg Nesterov <oleg@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v3 0/4] ftrace: Add a ftrace test collection
Date: Thu, 04 Sep 2014 11:42:51 +0900	[thread overview]
Message-ID: <87iol49kd0.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20140902110632.3207.20043.stgit@kbuild-f20.novalocal> (Masami Hiramatsu's message of "Tue, 02 Sep 2014 11:06:32 +0000")

On Tue, 02 Sep 2014 11:06:32 +0000, Masami Hiramatsu wrote:
> Hi,
>
> Here is the collection of testcases for ftrace version 3.
> This is just some updates and fixes according to the 
> discussion at previous version.
>   https://lkml.org/lkml/2014/8/26/304
>
> The major updates are:
>  - Fix some expressions to work on dash (Thanks Luis!)
>  - Support UNRESOLVED/UNTESTED/UNSUPPORTED results for testcase.
>    Those are POSIX 1003.3 standard.
>    (see http://www.gnu.org/software/dejagnu/manual/x47.html for
>     more details)
>  - Fix to show error logs.
>
> ftracetest is a small dash script for testing ftrace features.
> It will be required to add a unit test for each new feature
> after this is merged, because of preventing feature regressions.
>
> This version still be out of the selftest. However, at the kernel
> summit, I talked with Shuah about that. And since the kselftest
> will be the standard kernel unit test framework, I agreed to
> move this under the selftest. But I also would like to ask Steven
> and Namhyung to agree with it before moving.
>
> Actually, since we've already has similar shell-script base
> testcase under kselftest, we can easily move this under
> selftests.

By [k]selftest, did you mean tools/testing/selftests/ ?

Anyway I have no objection to the move.

Thanks for your work!
Namhyung

  parent reply	other threads:[~2014-09-04  2:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 11:06 Masami Hiramatsu
2014-09-02 11:06 ` [RFC PATCH v3 1/4] ftracetest: Initial commit for ftracetest Masami Hiramatsu
2014-09-04  1:41   ` Namhyung Kim
2014-09-04  1:48     ` Masami Hiramatsu
2014-09-16 22:21   ` Steven Rostedt
2014-09-17  5:40     ` Masami Hiramatsu
2014-09-02 11:06 ` [RFC PATCH v3 2/4] ftracetest: Add ftrace basic testcases Masami Hiramatsu
2014-09-02 11:06 ` [RFC PATCH v3 3/4] ftracetest: Add kprobe " Masami Hiramatsu
2014-09-02 11:06 ` [RFC PATCH v3 4/4] ftracetest: Add XFAIL/XPASS and POSIX.3 std. result codes Masami Hiramatsu
2014-09-04  2:29   ` Namhyung Kim
2014-09-04  4:39     ` Masami Hiramatsu
2014-09-08 10:41       ` Masami Hiramatsu
2014-09-04  2:42 ` Namhyung Kim [this message]
2014-09-04  3:57   ` Re: [RFC PATCH v3 0/4] ftrace: Add a ftrace test collection Masami Hiramatsu

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=87iol49kd0.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=shuah.kh@samsung.com \
    --cc=tom.zanussi@linux.intel.com \
    --cc=yoshihiro.yunomae.ez@hitachi.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

Powered by JetHome