mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@redhat.com>, Jiri Olsa <jolsa@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trace: Fix build breakage without CONFIG_PERF_EVENTS
Date: Wed, 11 Apr 2012 08:18:50 -0400	[thread overview]
Message-ID: <1334146730.23924.238.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1334132429-6091-1-git-send-email-broonie@opensource.wolfsonmicro.com>

Hi Mark,

Please change your subject when you submit a new patch. I've ignored
your last one because I thought I already applied it.

Your first patch:

  http://marc.info/?l=linux-kernel&m=133042701226637

Which was applied:

  https://lkml.org/lkml/2012/3/14/304


Your second patch:

  https://lkml.org/lkml/2012/3/26/164

As with this one, has the same subject. I only noticed it as I was about
to tell you that it was already applied.

Thanks,

-- Steve


On Wed, 2012-04-11 at 09:20 +0100, Mark Brown wrote:
> Today's -next fails to link for me:
> 
> kernel/built-in.o:(.data+0x178e50): undefined reference to `perf_ftrace_event_register'
> 
> It looks like multiple fixes have been merged for the issue fixed by
> commit fa73dc9 (tracing: Fix build breakage without CONFIG_PERF_EVENTS)
> though I can't identify the other changes that have gone in at the
> minute, it's possible that the changes which caused the breakage fixed
> by the previous commit got dropped but the fix made it in.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>  kernel/trace/trace.h |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
> index 95059f0..ff639ca 100644
> --- a/kernel/trace/trace.h
> +++ b/kernel/trace/trace.h
> @@ -836,11 +836,15 @@ extern const char *__stop___trace_bprintk_fmt[];
>  		     filter)
>  #include "trace_entries.h"
>  
> +#ifdef CONFIG_PERF_EVENTS
>  #ifdef 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 /* CONFIG_FUNCTION_TRACER */
> +#else
> +#define perf_ftrace_event_register NULL
> +#endif /* CONFIG_PERF_EVENTS */
>  
>  #endif /* _LINUX_KERNEL_TRACE_H */



  reply	other threads:[~2012-04-11 12:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11  8:20 Mark Brown
2012-04-11 12:18 ` Steven Rostedt [this message]
2012-04-12 18:36   ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2012-04-13  8:52 Mark Brown
2012-03-26 13:33 Mark Brown
2012-02-28 11:02 Mark Brown
2012-02-28 11:10 ` Mark Brown
2012-02-28 14:57   ` Jiri Olsa
2012-03-13 22:33     ` Steven Rostedt
2012-03-13 23:03     ` Jiri Olsa
2012-02-28 11:10 ` Mark Brown
2012-02-28 13:21 ` Jiri Olsa
2012-02-28 13:37   ` Mark Brown
2012-02-28 14:02     ` Steven Rostedt
2012-02-28 14:03       ` Mark Brown
2012-02-28 14:43         ` Jiri Olsa
2012-02-28 14:52           ` Steven Rostedt

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=1334146730.23924.238.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    /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®