From: Steven Rostedt <rostedt@goodmis•org>
To: Greg KH <greg@kroah•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Arnd Bergmann <arnd@arndb•de>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Tomas Winkler <tomas.winkler@intel•com>
Subject: [PATCH] mei: trace: Remove unused TRACE_SYSTEM_STRING define
Date: Mon, 13 Apr 2015 12:07:27 -0400 [thread overview]
Message-ID: <20150413120727.3bb82df0@gandalf.local.home> (raw)
In-Reply-To: <20150413104328.GB6390@kroah.com>
TRACE_SYSTEM_STRING is defined in mei-trace.h but is unused. Worse yet,
the ftrace tracing infrastructure is using it now and this causes
warnings about redefined macros.
Remove the define of TRACE_SYSTEM_STRING from mei-trace.h
Link: http://lkml.kernel.org/r/20150413193720.56083fbf@canb.auug.org.au
Reported-by: Stephen Rothwell <sfr@canb•auug.org.au>
Signed-off-by: Steven Rostedt <rostedt@goodmis•org>
---
diff --git a/drivers/misc/mei/mei-trace.h b/drivers/misc/mei/mei-trace.h
index 5f4e1a17360b..c9e24d2b698a 100644
--- a/drivers/misc/mei/mei-trace.h
+++ b/drivers/misc/mei/mei-trace.h
@@ -26,7 +26,6 @@
#undef TRACE_SYSTEM
#define TRACE_SYSTEM mei
-#define TRACE_SYSTEM_STRING __stringify(TRACE_SYSTEM)
TRACE_EVENT(mei_reg_read,
TP_PROTO(const struct device *dev, const char *reg, u32 offs, u32 val),
next prev parent reply other threads:[~2015-04-13 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 9:37 linux-next: build warnings after merge of the char-misc tree Stephen Rothwell
2015-04-13 10:43 ` Greg KH
2015-04-13 10:44 ` Winkler, Tomas
2015-04-13 10:47 ` Stephen Rothwell
2015-04-13 14:17 ` Steven Rostedt
2015-04-13 15:01 ` Steven Rostedt
2015-04-13 16:07 ` Steven Rostedt [this message]
2015-04-13 16:56 ` [PATCH] mei: trace: Remove unused TRACE_SYSTEM_STRING define Greg KH
2015-04-13 13:34 ` linux-next: build warnings after merge of the char-misc tree Greg KH
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=20150413120727.3bb82df0@gandalf.local.home \
--to=rostedt@goodmis$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tomas.winkler@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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