All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trace: Fix build breakage without CONFIG_PERF_EVENTS
Date: Tue, 28 Feb 2012 15:43:19 +0100	[thread overview]
Message-ID: <20120228144318.GF1694@m.brq.redhat.com> (raw)
In-Reply-To: <20120228140335.GM3683@opensource.wolfsonmicro.com>

On Tue, Feb 28, 2012 at 02:03:35PM +0000, Mark Brown wrote:
> On Tue, Feb 28, 2012 at 09:02:09AM -0500, Steven Rostedt wrote:
> > On Tue, 2012-02-28 at 13:37 +0000, Mark Brown wrote:
> 
> > > ARM.  If it was not possible to switch off PERF_EVENTS it shouldn't be a
> > > config option in the code as this is just creating complexity and
> > > potential breakage.
> 
> > It is possible to switch off PERF_EVENTS, just not on x86 :-/
> 
> Well, if you insist on using these restricted architectures :P

reproduced ;) looking for fix..

jirka


[jolsa@m tip]$ make   ARCH=arm CROSS_COMPILE=armv5tel-redhat-linux-gnueabi- uImage 
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
  CALL    scripts/checksyscalls.sh
  CHK     include/generated/compile.h
  CC      kernel/trace/trace_export.o
In file included from kernel/trace/trace_export.c:197:
kernel/trace/trace_entries.h:58: error: ‘perf_ftrace_event_register’
undeclared here (not in a function)
make[2]: *** [kernel/trace/trace_export.o] Error 1
make[1]: *** [kernel/trace] Error 2
make: *** [kernel] Error 2

  reply	other threads:[~2012-02-28 14:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 11:02 [PATCH] trace: Fix build breakage without CONFIG_PERF_EVENTS 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-03-22 21:21       ` [tip:perf/urgent] perf: Add ifdef to remove unused enum switch warnings tip-bot for Jiri Olsa
2012-02-28 11:10 ` [PATCH] trace: Fix build breakage without CONFIG_PERF_EVENTS 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 [this message]
2012-02-28 14:52           ` Steven Rostedt
2012-03-22 21:20 ` [tip:perf/urgent] tracing: " tip-bot for Mark Brown
2012-03-26 13:33 [PATCH] trace: " Mark Brown
2012-04-11  8:20 Mark Brown
2012-04-11 12:18 ` Steven Rostedt
2012-04-12 18:36   ` Mark Brown
2012-04-13  8:52 Mark Brown

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=20120228144318.GF1694@m.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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.