linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Tom Zanussi <tom.zanussi@linux.intel.com>,
	tglx@linutronix.de, namhyung@kernel.org, vedang.patel@intel.com,
	bigeasy@linutronix.de, joel.opensrc@gmail.com, joelaf@google.com,
	mathieu.desnoyers@efficios.com, baohong.liu@intel.com,
	rajvi.jingar@intel.com, julia@ni.com, fengguang.wu@intel.com,
	linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH 0/2] selftests: tracing: Update inter-event testcases
Date: Tue, 24 Apr 2018 15:22:21 -0400	[thread overview]
Message-ID: <20180424152221.7049b706@gandalf.local.home> (raw)
In-Reply-To: <152292049091.15769.13306554953968999494.stgit@devbox>

On Thu,  5 Apr 2018 18:28:11 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:

> Hi,
> 
> I've fixed a testcase for inter-event extended error
> and added a testcase for multiple actions on trigger,
> which is based on what Tom shown in his mail.
> 
> This series can be applied on Steven's tracing repo.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
> ftrace/core
> 
> Tom, could you review it?

Even without Tom's review. I took both patches.

Thanks Masami!

-- Steve

  parent reply	other threads:[~2018-04-24 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05  9:28 [PATCH 0/2] selftests: tracing: Update inter-event testcases Masami Hiramatsu
2018-04-05  9:28 ` [PATCH 1/2] selftests: ftrace: Fix trigger extended error testcase Masami Hiramatsu
2018-04-05  9:29 ` [PATCH 2/2] selftests: ftrace: Add a testcase for multiple actions on trigger Masami Hiramatsu
2018-04-24 19:22 ` Steven Rostedt [this message]
2018-04-24 22:24   ` [PATCH 0/2] selftests: tracing: Update inter-event testcases Tom Zanussi

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=20180424152221.7049b706@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=baohong.liu@intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=fengguang.wu@intel.com \
    --cc=joel.opensrc@gmail.com \
    --cc=joelaf@google.com \
    --cc=julia@ni.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=rajvi.jingar@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tom.zanussi@linux.intel.com \
    --cc=vedang.patel@intel.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).