From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Frédéric Weisbecker" <fweisbec@gmail.com>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [PATCH] ftrace: fix current_tracer error return
Date: Wed, 29 Oct 2008 09:35:41 +0100 [thread overview]
Message-ID: <20081029083541.GD6364@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0810282111000.26466@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Wed, 29 Oct 2008, Fr?d?ric Weisbecker wrote:
> > >> Thanks. I guess this bug was there for several days. But since I
> > >
> > > But this was not a bug :-/
> > >
> > > I believe I purposely set it that way. The bug was that you did not know
> > > that you could enable it with /proc/sys/kernel/ftrace_enabled ;-)
> >
> > Ah ok. I better understand now.
> > But IMHO I guess that would better for developpers who will use
> > it to have something directly enabled whithout touching this file at each start.
>
> Yep, and that's why I have no objections with the patch ;-)
it's in tracing/urgent now, so all should be well now.
Ingo
prev parent reply other threads:[~2008-10-29 8:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 23:18 Ftrace doesn't work anymore on latest tip Frédéric Weisbecker
2008-10-27 23:36 ` Steven Rostedt
2008-10-27 23:44 ` Frédéric Weisbecker
2008-10-28 9:02 ` Frédéric Weisbecker
2008-10-28 14:23 ` Steven Rostedt
2008-10-28 14:44 ` [PATCH] ftrace: fix current_tracer error return Steven Rostedt
2008-10-28 15:35 ` Frédéric Weisbecker
2008-10-28 15:41 ` Steven Rostedt
2008-10-28 18:15 ` Frédéric Weisbecker
2008-10-28 18:32 ` Steven Rostedt
2008-10-29 0:34 ` Frédéric Weisbecker
2008-10-29 0:55 ` Steven Rostedt
2008-10-29 1:09 ` Frédéric Weisbecker
2008-10-29 1:11 ` Steven Rostedt
2008-10-29 8:35 ` 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=20081029083541.GD6364@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.