From: Johannes Berg <johannes@sipsolutions.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Move message tracepoints to their own header
Date: Tue, 07 Apr 2015 16:28:46 +0200 [thread overview]
Message-ID: <1428416926.1841.17.camel@sipsolutions.net> (raw)
In-Reply-To: <20150407102146.216cf90b@gandalf.local.home>
On Tue, 2015-04-07 at 10:21 -0400, Steven Rostedt wrote:
> On Tue, 07 Apr 2015 08:58:58 +0200
> Johannes Berg <johannes@sipsolutions.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
next prev parent reply other threads:[~2015-04-07 14:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 3:13 [PATCH] mac80211: Move message tracepoints to their own header Steven Rostedt
2015-04-07 6:58 ` Johannes Berg
2015-04-07 12:55 ` Steven Rostedt
2015-04-07 13:40 ` Johannes Berg
2015-04-07 14:21 ` Steven Rostedt
2015-04-07 14:28 ` Johannes Berg [this message]
2015-04-07 16:13 ` [PATCH] iwlwifi: Move each system " Steven Rostedt
2015-04-08 7:44 ` Johannes Berg
2015-04-12 17:37 ` Emmanuel Grumbach
2015-04-13 6:22 ` Emmanuel Grumbach
2015-04-13 8:17 ` Emmanuel Grumbach
2015-04-13 15:05 ` 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=1428416926.1841.17.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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.