From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: rostedt@goodmis.org
Cc: pebolle@tiscali.nl, hiralpat@cisco.com, hishah@cisco.com,
linux-kernel@vger.kernel.org,
Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH v2 2/7] kallsyms: Add module.h include
Date: Mon, 13 Apr 2015 19:27:24 -0500 [thread overview]
Message-ID: <39f0b7eb7c21c9f5ea798bf912fb126032cef5e5.1428969546.git.tom.zanussi@linux.intel.com> (raw)
In-Reply-To: <cover.1428969546.git.tom.zanussi@linux.intel.com>
In-Reply-To: <cover.1428969546.git.tom.zanussi@linux.intel.com>
KSYM_SYMBOL_LEN uses MODULE_NAME_LEN defined in module.h, so include
module.h so users don't have to.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
---
include/linux/kallsyms.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/kallsyms.h b/include/linux/kallsyms.h
index 6883e19..e1550a4 100644
--- a/include/linux/kallsyms.h
+++ b/include/linux/kallsyms.h
@@ -8,6 +8,7 @@
#include <linux/errno.h>
#include <linux/kernel.h>
#include <linux/stddef.h>
+#include <linux/module.h>
#define KSYM_NAME_LEN 128
#define KSYM_SYMBOL_LEN (sizeof("%s+%#lx/%#lx [%s]") + (KSYM_NAME_LEN - 1) + \
--
1.9.3
next prev parent reply other threads:[~2015-04-14 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 0:27 [PATCH v2 0/7] kallsyms header cleanup Tom Zanussi
2015-04-14 0:27 ` [PATCH v2 1/7] tracing: Remove kallsyms.h include from linux/ftrace.h Tom Zanussi
2015-04-14 0:27 ` Tom Zanussi [this message]
2015-04-14 0:27 ` [PATCH v2 3/7] tracing: Remove redundant module.h includes Tom Zanussi
2015-04-14 0:27 ` [PATCH v2 4/7] lib: " Tom Zanussi
2015-04-14 0:27 ` [PATCH v2 5/7] fnic: " Tom Zanussi
2015-04-14 0:27 ` [PATCH v2 6/7] slub: " Tom Zanussi
2015-04-14 0:46 ` David Rientjes
2015-04-14 0:27 ` [PATCH v2 7/7] tracing: Remove unnecessary kallsyms.h and " Tom Zanussi
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=39f0b7eb7c21c9f5ea798bf912fb126032cef5e5.1428969546.git.tom.zanussi@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=hiralpat@cisco.com \
--cc=hishah@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--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
all inboxes | Powered by JetHome®