linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Viktor Rosendahl <viktor.rosendahl@gmail.com>
Cc: Joel Fernandes <joel@joelfernandes.org>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 4/4] ftrace: Add an option for tracing console latencies
Date: Thu, 10 Oct 2019 09:06:34 -0400	[thread overview]
Message-ID: <20191010090634.721d1a3b@gandalf.local.home> (raw)
In-Reply-To: <CAPQh3wO1zvwQf0zmb9_ro1spUo+CCxJFCgB2aQJWVW8KZoXQdA@mail.gmail.com>

On Thu, 10 Oct 2019 09:57:31 +0200
Viktor Rosendahl <viktor.rosendahl@gmail.com> wrote:

> Sounds good to me. I will try to adjust the patch accordingly within a few days.

OK,

Also, I may hold off on patch 3. I want to make sure that adding a new
directory to tools is OK, and see if there's not other things we can
add there.

-- Steve

      reply	other threads:[~2019-10-10 13:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 22:08 [PATCH v8 0/4] Some new features for the preempt/irqsoff tracers Viktor Rosendahl (BMW)
2019-10-08 22:08 ` [PATCH v8 1/4] ftrace: Implement fs notification for tracing_max_latency Viktor Rosendahl (BMW)
2019-10-08 22:08 ` [PATCH v8 2/4] preemptirq_delay_test: Add the burst feature and a sysfs trigger Viktor Rosendahl (BMW)
2019-10-08 22:08 ` [PATCH v8 3/4] Add the latency-collector to tools Viktor Rosendahl (BMW)
2019-10-08 22:08 ` [PATCH v8 4/4] ftrace: Add an option for tracing console latencies Viktor Rosendahl (BMW)
2019-10-09 14:11   ` Joel Fernandes
2019-10-09 14:51     ` Viktor Rosendahl
2019-10-09 18:08       ` Steven Rostedt
2019-10-10  7:57         ` Viktor Rosendahl
2019-10-10 13:06           ` Steven Rostedt [this message]

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=20191010090634.721d1a3b@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=viktor.rosendahl@gmail.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).