From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Joel Fernandes <joel@joelfernandes.org>,
Peter Zijlstra <peterz@infradead.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Tom Zanussi <zanussi@kernel.org>
Subject: Re: [PATCH 0/4 v2] tracing: Add a way to have custom events in the tracefs directory
Date: Thu, 3 Mar 2022 17:00:00 -0500 [thread overview]
Message-ID: <20220303170000.1f4f0f2e@gandalf.local.home> (raw)
In-Reply-To: <20220303214832.031378059@goodmis.org>
On Thu, 03 Mar 2022 16:48:32 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> #define TRACE_INCLUDE_FILE trace_custom_sched
> #include <trace/define_custom_trace.h>
> ------------------------->%-------------------------
It appears that I forgot to do a:
git add include/trace/trace_custom_events.h include/trace/define_custom_trace.h
and those two very important files are missing from the last patch.
Will send a v3.
-- Steve
prev parent reply other threads:[~2022-03-03 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 21:48 [PATCH 0/4 v2] tracing: Add a way to have custom events in the tracefs directory Steven Rostedt
2022-03-03 21:48 ` [PATCH 1/4 v2] tracing: Allow custom events to be added to " Steven Rostedt
2022-03-03 21:48 ` [PATCH 2/4 v2] tracing: Add sample code for custom trace events Steven Rostedt
2022-03-03 21:48 ` [PATCH 3/4 v2] tracing: Move the defines to create TRACE_EVENTS into their own files Steven Rostedt
2022-03-03 21:48 ` [PATCH 4/4 v2] tracing: Add TRACE_CUSTOM_EVENT() macro Steven Rostedt
2022-03-03 22:00 ` Steven Rostedt [this message]
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=20220303170000.1f4f0f2e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=zanussi@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).