linux-kernel - Re: [PATCH] mac80211: Move message 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1428416926.1841.17.camel@sipsolutions.net>
Date:	Tue, 07 Apr 2015 16:28:46 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, linux-wireless@...r.kernel.org
Subject: Re: [PATCH] mac80211: Move message tracepoints to their own header

On Tue, 2015-04-07 at 10:21 -0400, Steven Rostedt wrote:
> On Tue, 07 Apr 2015 08:58:58 +0200
> Johannes Berg <johannes@...solutions.net> wrote:
> 
> > On Mon, 2015-04-06 at 23:13 -0400, Steven Rostedt wrote:
> > > Every tracing file must have its own TRACE_SYSTEM defined.
> > 
> > Oh, that requirement is new to me. I also have the same in iwlwifi, with
> > even more TRACE_SYSTEMs.
> 
> OK, the reason I did not stumble over this is because the previous
> patch broke the build before I got here.
> 
> During my latest tests, this breaks it too.
> 
> You OK if I make more patches to split that file apart?

Sure, no problem. I don't think we have any work on them that could
possibly conflict now.

johannes

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