linux-kernel - Re: [PATCH][GIT PULL][v3.4] tracing: Fix build breakage without CONFIG_PERF

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1334324244.23924.357.camel@gandalf.stny.rr.com>
Date:	Fri, 13 Apr 2012 09:37:24 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Jiri Olsa <jolsa@...hat.com>
Subject: Re: [PATCH][GIT PULL][v3.4] tracing: Fix build breakage without
 CONFIG_PERF_EVENTS (again)

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/