mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [PATCH 0/2] [GIT PULL] tracing: updates for tip
Date: Sat, 9 May 2009 06:27:14 +0200	[thread overview]
Message-ID: <20090509042714.GE8007@elte.hu> (raw)
In-Reply-To: <20090508203605.361898511@goodmis.org>


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

> Ingo,
> 
> The first patch fixes a uninitialized variable. What bothers me 
> about this, is that gcc did not warn about it. My gcc warns about 
> a ton of variables that might not being initialized, but missed 
> one that actually is not!
> 
> I wonder if it is only my version of gcc:  4.2.2
> :-/
> 
> Please pull the latest tip/tracing/ftrace-1 tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/ftrace-1
> 
> 
> Steven Rostedt (2):
>       tracing: initialize return value for __ftrace_set_clr_event
>       tracing: add trace_set_clr_event to export event enabling function
> 
> ----
>  include/linux/ftrace_event.h |    2 ++
>  kernel/trace/trace_events.c  |   19 ++++++++++++++++++-
>  2 files changed, 20 insertions(+), 1 deletions(-)

Pulled, thanks Steve!

Note, the above branch gave conflicts in ring_buffer.c. But i pulled 
at commit 4671c79 from your tree which gave the same diffstat:

 Fast forward
  include/linux/ftrace_event.h |    2 ++
  kernel/trace/trace_events.c  |   19 ++++++++++++++++++-
  2 files changed, 20 insertions(+), 1 deletions(-)

Please double-check that i got the right bits. Thanks,

	Ingo

      parent reply	other threads:[~2009-05-09  4:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 20:36 Steven Rostedt
2009-05-08 20:36 ` [PATCH 1/2] tracing: initialize return value for __ftrace_set_clr_event Steven Rostedt
2009-05-10  6:19   ` Li Zefan
2009-05-08 20:36 ` [PATCH 2/2] tracing: add trace_set_clr_event to export event enabling function Steven Rostedt
2009-05-09  4:27 ` 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=20090509042714.GE8007@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --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

Powered by JetHome