From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>, linux-wireless@vger.kernel.org
Subject: [PATCH 2/2] compat: add stub headers linux/tracepoint.h and trace/define_trace.h
Date: Tue, 06 Apr 2010 18:41:15 -0400 [thread overview]
Message-ID: <20100406224115.2937.89309.stgit@mj.roinet.com> (raw)
In-Reply-To: <20100406224109.2937.65315.stgit@mj.roinet.com>
This should make 13-trace.patch in compat-wireless unnecessary.
Signed-off-by: Pavel Roskin <proski@gnu.org>
---
include/linux/tracepoint.h | 8 ++++++++
include/trace/define_trace.h | 8 ++++++++
2 files changed, 16 insertions(+), 0 deletions(-)
create mode 100644 include/linux/tracepoint.h
create mode 100644 include/trace/define_trace.h
diff --git a/include/linux/tracepoint.h b/include/linux/tracepoint.h
new file mode 100644
index 0000000..7484716
--- /dev/null
+++ b/include/linux/tracepoint.h
@@ -0,0 +1,8 @@
+#ifndef _COMPAT_LINUX_TRACEPOINT_H
+#define _COMPAT_LINUX_TRACEPOINT_H 1
+
+#if (LINUX_VERSION_CODE > KERNEL_VERSION(2,6,27))
+#include_next <linux/tracepoint.h>
+#endif /* (LINUX_VERSION_CODE > KERNEL_VERSION(2,6,27)) */
+
+#endif /* _COMPAT_LINUX_TRACEPOINT_H */
diff --git a/include/trace/define_trace.h b/include/trace/define_trace.h
new file mode 100644
index 0000000..f5c01de
--- /dev/null
+++ b/include/trace/define_trace.h
@@ -0,0 +1,8 @@
+#ifndef _COMPAT_TRACE_DEFINE_TRACE_H
+#define _COMPAT_TRACE_DEFINE_TRACE_H 1
+
+#if (LINUX_VERSION_CODE > KERNEL_VERSION(2,6,30))
+#include_next <trace/define_trace.h>
+#endif /* (LINUX_VERSION_CODE > KERNEL_VERSION(2,6,30)) */
+
+#endif /* _COMPAT_TRACE_DEFINE_TRACE_H */
next prev parent reply other threads:[~2010-04-06 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 22:41 [PATCH 1/2] compat: add device_create() implementation for Linux 2.6.26 and older Pavel Roskin
2010-04-06 22:41 ` Pavel Roskin [this message]
2010-04-06 23:34 ` [PATCH 2/2] compat: add stub headers linux/tracepoint.h and trace/define_trace.h Luis R. Rodriguez
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=20100406224115.2937.89309.stgit@mj.roinet.com \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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).