public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Carsten Emde <Carsten.Emde@osadl.org>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	rostedt@goodmis.org, tglx@linutronix.de,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:tracing/urgent] tracing: Fix trace_marker output
Date: Sun, 6 Dec 2009 11:50:27 -0600	[thread overview]
Message-ID: <20091206175027.GA9095@lixom.net> (raw)
In-Reply-To: <4B1BAB74.104@osadl.org>

On Sun, Dec 06, 2009 at 02:02:44PM +0100, Carsten Emde wrote:
> Olof,
> 
[...]
> Having looked at other possible solutions, I find that the best thing to do
> is to revert this part of the patch. Sorry that I didn't check it on ARM
> platforms.

Thanks, no worries. I figured there was a better way to fix it but
including a bad patch tends to be better than not including one :)


-Olof


  reply	other threads:[~2009-12-06 17:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 19:56 [PATCH] ftrace: fix trace_marker output Carsten Emde
2009-11-16 22:15 ` Steven Rostedt
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 [this message]
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=20091206175027.GA9095@lixom.net \
    --to=olof@lixom.net \
    --cc=Carsten.Emde@osadl.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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