All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Tom Zanussi <tom.zanussi@linux.intel.com>,
	Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>,
	Oleg Nesterov <oleg@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/3] ftrace: Add a ftrace test collection
Date: Wed, 13 Aug 2014 16:14:56 +0900	[thread overview]
Message-ID: <87tx5gdfnz.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <8738d0euyv.fsf@sejong.aot.lge.com> (Namhyung Kim's message of "Wed, 13 Aug 2014 15:59:04 +0900")

On Wed, 13 Aug 2014 15:59:04 +0900, Namhyung Kim wrote:
> On Tue, 5 Aug 2014 17:37:52 -0400, Steven Rostedt wrote:
>> Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:
>>>  - What's the good naming method of testcases?
>
> I'm okay with the ftracetest, but tracing-test may be an option. :)

Ouch, did you say about *.tc file name?  I have no problem with that too
anyway :)

Thanks,
Namhyung

  reply	other threads:[~2014-08-13  7:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05  2:45 [RFC PATCH 0/3] ftrace: Add a ftrace test collection Masami Hiramatsu
2014-08-05  2:45 ` [RFC PATCH 1/3] ftracetest: Initial commit for ftracetest Masami Hiramatsu
2014-08-05  2:45 ` [RFC PATCH 2/3] ftracetest: Add ftrace basic testcases Masami Hiramatsu
2014-08-05  2:46 ` [RFC PATCH 3/3] ftracetest: Add kprobe " Masami Hiramatsu
2014-08-05 21:37 ` [RFC PATCH 0/3] ftrace: Add a ftrace test collection Steven Rostedt
2014-08-07  4:53   ` Masami Hiramatsu
2014-08-13  6:59   ` Namhyung Kim
2014-08-13  7:14     ` Namhyung Kim [this message]
2014-08-13 15:54     ` 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=87tx5gdfnz.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.