From: Jiri Olsa <jolsa@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/3] tracing: removing struct module* parameter from ftrace_init_module code path
Date: Sun, 19 Jul 2009 20:47:19 +0200 [thread overview]
Message-ID: <20090719184719.GA3040@jolsa.redhat.com> (raw)
In-Reply-To: <20090718101653.GC24164@elte.hu>
On Sat, Jul 18, 2009 at 12:16:53PM +0200, Ingo Molnar wrote:
>
> * jolsa@redhat.com <jolsa@redhat.com> wrote:
>
> > The "struct module*" is not being used in the ftrace_init_module
> > code path, removing it.
> >
> > wbr,
> > jirka
> >
> > Signed-off-by: Jiri Olsa <jolsa@redhat.com>
> >
> > ---
> > arch/x86/kernel/ftrace.c | 3 +--
> > include/linux/ftrace.h | 4 +---
> > kernel/trace/ftrace.c | 25 +++++++++++--------------
> > 3 files changed, 13 insertions(+), 19 deletions(-)
>
> patch didnt apply cleanly to the latest tracing tree:
>
> http://people.redhat.com/mingo/tip.git/README
>
> and the other bits had some fuzz as well. Mind merging + resending
> this?
>
> Ingo
sure, np.. I made it against the linus' tree, I'll use the
tip tree next time
jira
next prev parent reply other threads:[~2009-07-19 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 19:44 [PATCH 0/3] tracing: minor bugs jolsa
2009-07-16 19:44 ` [PATCH 1/3] tracing: removing not used variables jolsa
2009-07-18 10:24 ` [tip:tracing/core] tracing: Remove unused fields/variables tip-bot for jolsa@redhat.com
2009-07-16 19:44 ` [PATCH 2/3] tracing: removing struct module* parameter from ftrace_init_module code path jolsa
2009-07-18 10:16 ` Ingo Molnar
2009-07-19 18:47 ` Jiri Olsa [this message]
2009-07-16 19:44 ` [PATCH 3/3] tracing: removing .globl in the scripts/recordmcount.pl doc jolsa
2009-07-18 10:24 ` [tip:tracing/core] tracing: Remove " tip-bot for jolsa@redhat.com
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=20090719184719.GA3040@jolsa.redhat.com \
--to=jolsa@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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