From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: linux-kernel@vger.kernel.org
Cc: linux-arch@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org
Subject: [PATCH 08/14] m68k: migrate exception table users off module.h and onto extable.h
Date: Sun, 24 Jul 2016 23:42:41 -0400 [thread overview]
Message-ID: <20160725034247.109173-9-paul.gortmaker@windriver.com> (raw)
In-Reply-To: <20160725034247.109173-1-paul.gortmaker@windriver.com>
This file was only including module.h for exception table related
functions. We've now separated that content out into its own file
"extable.h" so now move over to that and avoid all the extra header
content in module.h that we don't really need to compile this.
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
---
arch/m68k/kernel/signal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/m68k/kernel/signal.c b/arch/m68k/kernel/signal.c
index 2dcee3a88867..db775322b485 100644
--- a/arch/m68k/kernel/signal.c
+++ b/arch/m68k/kernel/signal.c
@@ -42,7 +42,7 @@
#include <linux/personality.h>
#include <linux/tty.h>
#include <linux/binfmts.h>
-#include <linux/module.h>
+#include <linux/extable.h>
#include <linux/tracehook.h>
#include <asm/setup.h>
--
2.8.4
next prev parent reply other threads:[~2016-07-25 3:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 3:42 [RFC/PATCH 00/14] split exception table content out of module.h into extable.h Paul Gortmaker
2016-07-25 3:42 ` Paul Gortmaker
2016-07-25 3:42 ` [PATCH 01/14] exceptions: fork exception table content from " Paul Gortmaker
2016-07-25 3:42 ` Paul Gortmaker
2016-07-27 2:34 ` Rusty Russell
2016-07-27 2:34 ` Rusty Russell
2016-07-25 3:42 ` [PATCH 02/14] x86: migrate exception table users off module.h and onto extable.h Paul Gortmaker
2016-07-25 3:42 ` Paul Gortmaker
2016-07-25 6:35 ` Ingo Molnar
2016-07-25 3:42 ` [PATCH 03/14] arm: " Paul Gortmaker
2016-07-25 3:42 ` Paul Gortmaker
2016-07-25 3:42 ` [PATCH 04/14] arm64: " Paul Gortmaker
2016-07-25 16:03 ` Catalin Marinas
2016-07-25 3:42 ` [PATCH 05/14] mips: " Paul Gortmaker
2016-07-25 9:08 ` kbuild test robot
2016-07-25 9:08 ` kbuild test robot
2016-07-25 3:42 ` [PATCH 06/14] sparc: " Paul Gortmaker
2016-07-25 3:42 ` Paul Gortmaker
2016-07-25 3:42 ` [PATCH 07/14] powerpc: " Paul Gortmaker
2016-07-25 3:42 ` Paul Gortmaker [this message]
2016-07-25 3:42 ` [PATCH 09/14] s390: " Paul Gortmaker
2016-07-25 3:42 ` [PATCH 10/14] tile: " Paul Gortmaker
2016-07-25 3:42 ` [PATCH 11/14] alpha: " Paul Gortmaker
2016-07-25 3:42 ` Paul Gortmaker
2016-07-25 3:42 ` [PATCH 12/14] parisc: " Paul Gortmaker
2016-07-25 3:42 ` Paul Gortmaker
2016-07-25 3:42 ` [PATCH 13/14] core: " Paul Gortmaker
2016-07-25 3:42 ` [PATCH 14/14] module.h: remove extable.h include now users have migrated Paul Gortmaker
2016-07-25 4:18 ` [RFC/PATCH 00/14] split exception table content out of module.h into extable.h Linus Torvalds
2016-07-25 4:18 ` Linus Torvalds
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=20160725034247.109173-9-paul.gortmaker@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).