linux-kernel - [char-misc-next] mei: trace: remove unused TRACE_SYSTEM

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>] [day] [month] [year] [list]

Message-Id: <1428922580-7139-1-git-send-email-tomas.winkler@intel.com>
Date:	Mon, 13 Apr 2015 13:56:20 +0300
From:	Tomas Winkler <tomas.winkler@...el.com>
To:	gregkh@...uxfoundation.org
Cc:	arnd@...db.de, linux-kernel@...r.kernel.org,
	Tomas Winkler <tomas.winkler@...el.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: [char-misc-next] mei: trace: remove unused TRACE_SYSTEM_STRING

fix warning:
include/trace/ftrace.h:28:0: note: this is the location of the previous definition
 ^
In file included from include/trace/define_trace.h:90:0,
                 from drivers/misc/mei/mei-trace.h:76,
                 from drivers/misc/mei/mei-trace.c:21:
include/trace/ftrace.h:28:0: warning: "TRACE_SYSTEM_STRING" redefined

Cc: Stephen Rothwell <sfr@...b.auug.org.au>
Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
Signed-off-by: Tomas Winkler <tomas.winkler@...el.com>
---
 drivers/misc/mei/mei-trace.h | 2 --
 1 file changed, 2 deletions(-)

diff --git a/drivers/misc/mei/mei-trace.h b/drivers/misc/mei/mei-trace.h
index 5f4e1a17360b..47e1bc6551d4 100644
--- a/drivers/misc/mei/mei-trace.h
+++ b/drivers/misc/mei/mei-trace.h
@@ -24,9 +24,7 @@
 #include <linux/device.h>
 
 #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),
-- 
1.9.3

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