[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tip-19348e749e9515c429f5d561d2f2c724862a4bee@git.kernel.org>
Date: Thu, 14 Feb 2013 13:01:58 -0800
From: tip-bot for Paul Gortmaker <paul.gortmaker@...driver.com>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...nel.org,
trivial@...nel.org, tglx@...utronix.de, hpa@...ux.intel.com,
paul.gortmaker@...driver.com
Subject: [tip:x86/cleanups] x86:
ptrace.c only needs export.h and not the full module.h
Commit-ID: 19348e749e9515c429f5d561d2f2c724862a4bee
Gitweb: http://git.kernel.org/tip/19348e749e9515c429f5d561d2f2c724862a4bee
Author: Paul Gortmaker <paul.gortmaker@...driver.com>
AuthorDate: Thu, 14 Feb 2013 15:14:02 -0500
Committer: H. Peter Anvin <hpa@...ux.intel.com>
CommitDate: Thu, 14 Feb 2013 12:56:12 -0800
x86: ptrace.c only needs export.h and not the full module.h
Commit cb57a2b4cff7edf2a4e32c0163200e9434807e0a ("x86-32: Export
kernel_stack_pointer() for modules") added an include of the
module.h header in conjunction with adding an EXPORT_SYMBOL_GPL
of kernel_stack_pointer.
But module.h should be avoided for simple exports, since it in turn
includes the world. Swap the module.h for export.h instead.
Cc: Jiri Kosina <trivial@...nel.org>
Signed-off-by: Paul Gortmaker <paul.gortmaker@...driver.com>
Link: http://lkml.kernel.org/r/1360872842-28417-1-git-send-email-paul.gortmaker@windriver.com
Signed-off-by: H. Peter Anvin <hpa@...ux.intel.com>
---
arch/x86/kernel/ptrace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/ptrace.c b/arch/x86/kernel/ptrace.c
index b629bbe..29a8120 100644
--- a/arch/x86/kernel/ptrace.c
+++ b/arch/x86/kernel/ptrace.c
@@ -22,7 +22,7 @@
#include <linux/perf_event.h>
#include <linux/hw_breakpoint.h>
#include <linux/rcupdate.h>
-#include <linux/module.h>
+#include <linux/export.h>
#include <linux/context_tracking.h>
#include <asm/uaccess.h>
--
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/
Powered by blists - more mailing lists