linux-kernel - Re: [PATCH] brcmsmac: Move each system tracepoints to their own header

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: <20150408074910.7563a1c8@gandalf.local.home>
Date:	Wed, 8 Apr 2015 07:49:10 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	<linux-wireless@...r.kernel.org>
Subject: Re: [PATCH] brcmsmac: Move each system tracepoints to their own
 header

On Wed, 8 Apr 2015 09:32:44 +0200
Arend van Spriel <arend@...adcom.com> wrote:

> On 04/07/15 18:11, Steven Rostedt wrote:
> >
> > Every tracing file must have its own TRACE_SYSTEM defined.
> > The brcmsmac tracepoint header broke this and added in the middle
> > of the file:
> >
> >   #undef TRACE_SYSTEM
> >   #define TRACE_SYSTEM brcmsmac
> >
> >   #undef TRACE_SYSTEM
> >   #define TRACE_SYSTEM brcmsmac_tx
> >
> >   #undef TRACE_SYSTEM
> >   #define TRACE_SYSTEM brcmsmac_msg
> >
> > Unfortunately, this broke new code in the ftrace infrastructure.
> > Moving each of these TRACE_SYSTEMs into their own trace file with
> > just one TRACE_SYSTEM per file fixes the issue.
> >
> > Cc: Arend van Spriel<arend@...adcom.com>
> 
> All right. Go ahead and change Cc: into Acked-by:
> 

Thanks!

-- 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/