From: Ingo Molnar <mingo@elte.hu>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: rostedt@goodmis.org, akpm@linux-foundation.org,
fweisbec@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix writing to trace/trace_options
Date: Mon, 17 Nov 2008 12:08:24 +0100 [thread overview]
Message-ID: <20081117110824.GM28786@elte.hu> (raw)
In-Reply-To: <1226831883-26362-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
* Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> wrote:
> writing to trace/trace_options use the index of the array
> to find the value of the flag. With branch tracer flag
> defined conditionally, this breaks writing to trace_options
> with branch tracer disabled.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>
> ---
> kernel/trace/trace.c | 2 --
> kernel/trace/trace.h | 2 --
> 2 files changed, 0 insertions(+), 4 deletions(-)
applied to tip/tracing/branch-tracer, thanks Aneesh!
Ingo
prev parent reply other threads:[~2008-11-17 11:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 10:37 [PATCH] Fix writing to trace/trace_options Aneesh Kumar K.V
2008-11-16 10:37 ` [PATCH] ftrace: Add new entry type TRACE_BIN_DUMP Aneesh Kumar K.V
2008-11-16 10:38 ` [PATCH] ftrace: add proper bin iterator support Aneesh Kumar K.V
2008-11-16 10:38 ` [PATCH] ftrace: Add debug_dump trace to dump binary data from kernel to userspace Aneesh Kumar K.V
2008-11-16 10:38 ` [PATCH] ftrace: Add debug_print trace to print " Aneesh Kumar K.V
2008-11-16 10:38 ` [PATCH] ftrace: Add dump iteator Aneesh Kumar K.V
2008-11-16 10:46 ` [PATCH] Fix writing to trace/trace_options Aneesh Kumar K.V
2008-11-16 15:07 ` Steven Rostedt
2008-11-17 11:17 ` Ingo Molnar
2008-11-17 13:11 ` Aneesh Kumar K.V
2008-11-18 14:06 ` Ingo Molnar
2008-11-16 15:05 ` Steven Rostedt
2008-11-17 11:08 ` 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=20081117110824.GM28786@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.