mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Carsten Emde <Carsten.Emde@osadl.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] ftrace: fix trace_marker output
Date: Mon, 16 Nov 2009 17:15:57 -0500	[thread overview]
Message-ID: <1258409757.22249.457.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4B01AE5D.1010801@osadl.org>

On Mon, 2009-11-16 at 20:56 +0100, Carsten Emde wrote:
> When a string was written to <debugfs>/tracing/trace_marker, some
> strange characters appeared in the trace output instead of the
> string, since a vprint function erroneously called a vararg print
> function with a va_list argument. This patch fixes the problem and
> simplifies the related code.
> 
> Signed-off-by: Carsten Emde <C.Emde@osadl.org>

Thanks Carsten! I'll pull this in. Perhaps this should go into 32.

-- Steve




  reply	other threads:[~2009-11-16 22:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 19:56 Carsten Emde
2009-11-16 22:15 ` Steven Rostedt [this message]
2009-11-17 14:18 ` Steven Rostedt
2009-11-17 15:20 ` [PATCH][GIT PULL][v2.6.32] tracing: Fix " Steven Rostedt
2009-11-22 10:24 ` [tip:tracing/urgent] " tip-bot for Carsten Emde
2009-12-06  5:13   ` Olof Johansson
2009-12-06  9:24     ` Carsten Emde
2009-12-06 13:02     ` Carsten Emde
2009-12-06 17:50       ` Olof Johansson
2009-12-09  4:19       ` [PATCH][GIT PULL][v2.6.33] tracing: Remove comparing of NULL to va_list in trace_array_vprintk() Steven Rostedt
2009-12-09  5:56         ` Ingo Molnar
2009-12-09  6:11           ` Ingo Molnar
2009-12-09  6:15             ` Ingo Molnar
2009-12-09 14:06               ` Steven Rostedt
2009-12-09 18:05             ` Steven Rostedt
2009-12-10  7:49       ` [tip:tracing/core] " tip-bot for Carsten Emde

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=1258409757.22249.457.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=Carsten.Emde@osadl.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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
all inboxes | Powered by JetHome®