public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	johannes@sipsolutions.net, tglx@linutronix.de,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:tracing/urgent] tracing: Fix event format export
Date: Thu, 3 Dec 2009 15:55:04 +0100	[thread overview]
Message-ID: <20091203145504.GA959@elte.hu> (raw)
In-Reply-To: <1259851297.12870.134.camel@gandalf.stny.rr.com>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> On Sat, 2009-11-14 at 10:18 +0000, tip-bot for Johannes Berg wrote:
> > Commit-ID:  811cb50baf63461ce0bdb234927046131fc7fa8b
> > Gitweb:     http://git.kernel.org/tip/811cb50baf63461ce0bdb234927046131fc7fa8b
> > Author:     Johannes Berg <johannes@sipsolutions.net>
> > AuthorDate: Fri, 13 Nov 2009 23:40:09 +0100
> > Committer:  Steven Rostedt <rostedt@goodmis.org>
> > CommitDate: Fri, 13 Nov 2009 22:20:34 -0500
> > 
> > tracing: Fix event format export
> > 
> > For some reason the export of the event print format to userspace
> > uses '#fmt' which breaks if the format string is anything but a plain
> > string, for example if it is built with macros then the macro names
> > are exported instead of their contents.
> > 
> > Use
> > 	"\"%s\"", fmt
> > instead of
> > 	"%s", #fmt
> > to export the string and not the way it is built.
> > 
> > For example, in net/mac80211/driver-trace.h for the trace event drv_start
> > there is:
> > 
> >         TP_printk(
> >                 LOCAL_PR_FMT, LOCAL_PR_ARG
> >         )
> > 
> > Which use to produce:
> > 
> >  print fmt: LOCAL_PR_FMT, REC->wiphy_name
> > 
> > Now produces:
> > 
> >  print fmt: "%s", REC->wiphy_name
> > 
> > Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> > LKML-Reference: <20091113224009.GB23942@elte.hu>
> > Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> 
> 
> Ingo,
> 
> Any reason that this did not make it into Mainline? 2.6.32 is out, and 
> Johannes Berg was depending on this for his users.

Yeah, it narrowly missed the last -rc (-rc8), and we only push 
post-final-rc fixes for serious show-stopper regressions.

v2.6.32.1 will have this (and other) fixes. Johannes can cherry-pick the 
fix in a day or so once it hits Linus's tree in the merge window.

Thanks,

	Ingo

  reply	other threads:[~2009-12-03 14:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13 12:37 [PATCH 2.6.32] ftrace: fix event format export Johannes Berg
2009-11-13 13:22 ` Andreas Schwab
2009-11-13 13:29   ` Johannes Berg
2009-11-13 13:32     ` Johannes Berg
2009-11-13 22:40 ` Ingo Molnar
2009-11-13 23:28   ` Steven Rostedt
2009-11-14  9:21     ` Johannes Berg
2009-11-14  4:12   ` [PATCH][GIT PULL][v2.6.32] tracing: Fix " Steven Rostedt
2009-11-14  9:39     ` Ingo Molnar
2009-11-14 10:18   ` [tip:tracing/urgent] " tip-bot for Johannes Berg
2009-12-03 14:41     ` Steven Rostedt
2009-12-03 14:55       ` Ingo Molnar [this message]
2009-12-06 16:19         ` Johannes Berg
2009-12-06 17:11           ` Ingo Molnar

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=20091203145504.GA959@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=johannes@sipsolutions.net \
    --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