From: Wei Yang <richard.weiyang@linux.alibaba.com>
To: rostedt@goodmis.org, mingo@redhat.com
Cc: linux-kernel@vger.kernel.org,
Wei Yang <richard.weiyang@linux.alibaba.com>
Subject: [PATCH 2/4] tracing: not necessary re-define DEFINE_EVENT_PRINT
Date: Fri, 12 Jun 2020 17:28:42 +0800 [thread overview]
Message-ID: <20200612092844.56107-3-richard.weiyang@linux.alibaba.com> (raw)
In-Reply-To: <20200612092844.56107-1-richard.weiyang@linux.alibaba.com>
The definition of DEFINE_EVENT_PRINT is not changed after previous one,
so not necessary to re-define is as the same form.
Signed-off-by: Wei Yang <richard.weiyang@linux.alibaba.com>
---
include/trace/trace_events.h | 4 ----
1 file changed, 4 deletions(-)
diff --git a/include/trace/trace_events.h b/include/trace/trace_events.h
index a4994761bdaf..5219f81b9d74 100644
--- a/include/trace/trace_events.h
+++ b/include/trace/trace_events.h
@@ -520,10 +520,6 @@ static inline notrace int trace_event_get_offsets_##call( \
return __data_size; \
}
-#undef DEFINE_EVENT_PRINT
-#define DEFINE_EVENT_PRINT(template, name, proto, args, print) \
- DEFINE_EVENT(template, name, PARAMS(proto), PARAMS(args))
-
#include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
/*
--
2.20.1 (Apple Git-117)
next prev parent reply other threads:[~2020-06-12 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 9:28 [PATCH 0/4] tracing: cleanup trace event macro Wei Yang
2020-06-12 9:28 ` [PATCH 1/4] tracing: not necessary to undefine DEFINE_EVENT again Wei Yang
2020-06-12 9:28 ` Wei Yang [this message]
2020-06-12 9:28 ` [PATCH 3/4] tracing: define DEFINE_EVENT_PRINT not related to DEFINE_EVENT Wei Yang
2020-06-12 9:28 ` [PATCH 4/4] tracing: not necessary to define DEFINE_EVENT_PRINT to be empty again Wei Yang
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=20200612092844.56107-3-richard.weiyang@linux.alibaba.com \
--to=richard.weiyang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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).