public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Pekka Paalanen <pq@iki.fi>, Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [Patch -tip 1/3] Tracing/ftrace: Relay unhandled entry output
Date: Sat, 27 Sep 2008 19:53:46 +0200	[thread overview]
Message-ID: <20080927175346.GA1108@elte.hu> (raw)
In-Reply-To: <c62985530809250940s1cdab6dau87bee24b6bc6c089@mail.gmail.com>


* Frédéric Weisbecker <fweisbec@gmail.com> wrote:

> So, unless someone is opposed to. I will send a patch which define 
> three possible values for the print_line callback. I will define these 
> values on trace.h Why not:
> 
> #define TRACE_TYPE_PARTIAL_LINE 0
> #define TRACE_TYPE_HANDLED 1
> #define TRACE_TYPE_UNHANDLED 2   => will relay on default functions
> 
> Hmm I'm questionning about the relevance of this kind of patch since 
> the tracing API is in refactoring...

btw., i removed the 2 patches that got NAK-ed by Pekka from tip/master - 
could you please re-send whatever consensus patch you come up with 
Pekka?

	Ingo

      parent reply	other threads:[~2008-09-27 17:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25 12:19 [Patch -tip 1/3] Tracing/ftrace: Relay unhandled entry output Frédéric Weisbecker
2008-09-25 12:38 ` Ingo Molnar
2008-09-25 14:56   ` Frédéric Weisbecker
2008-09-25 15:09     ` Pekka Paalanen
2008-09-25 15:33       ` Frédéric Weisbecker
2008-09-25 15:49         ` Pekka Paalanen
2008-09-25 15:56           ` Frédéric Weisbecker
2008-09-25 16:01             ` Pekka Paalanen
2008-09-25 16:40               ` Frédéric Weisbecker
2008-09-27 17:50                 ` Ingo Molnar
2008-09-29  9:29                   ` Frédéric Weisbecker
2008-09-27 17:53                 ` Ingo Molnar [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=20080927175346.GA1108@elte.hu \
    --to=mingo@elte.hu \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pq@iki.fi \
    --cc=rostedt@goodmis.org \
    /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