From: Steven Rostedt <rostedt@goodmis.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH][GIT PULL][v3.4] tracing: Fix build breakage without CONFIG_PERF_EVENTS (again)
Date: Fri, 13 Apr 2012 09:37:24 -0400 [thread overview]
Message-ID: <1334324244.23924.357.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20120413085315.GC3168@opensource.wolfsonmicro.com>
On Fri, 2012-04-13 at 09:53 +0100, Mark Brown wrote:
> On Thu, Apr 12, 2012 at 04:39:53PM -0400, Steven Rostedt wrote:
>
> > Looking at this patch in more depth, it may be cleaner to do:
>
> > #if defined(CONFIG_PERF_EVENTS) && defined(CONFIG_FUNCTION_TRACER)
> > int perf_ftrace_event_register(struct ftrace_event_call *call,
> > enum trace_reg type, void *data);
> > #else
> > # define perf_ftrace_event_register NULL
> > #endif
>
> > Mark, would you like to make the above update?
>
> I've sent a revised version of the patch out. I really don't care which
> version gets merged or who writes the patch so long as we can get this
> fixed.
I know it's trivial, but people do get upset when one developer redoes
the work of another. But thanks! I'm adding it to my tree now and
testing it.
-- Steve
prev parent reply other threads:[~2012-04-13 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 20:25 Steven Rostedt
2012-04-12 20:39 ` Steven Rostedt
2012-04-13 8:53 ` Mark Brown
2012-04-13 13:37 ` Steven Rostedt [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=1334324244.23924.357.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®