浏览代码

h8300-use-generic-init_task

Same code. Use the generic version.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
Link: http://lkml.kernel.org/r/20120503085034.623666760@linutronix.de
Thomas Gleixner 13 年之前
父节点
当前提交
a3b3aa3d9d
共有 3 个文件被更改,包括 2 次插入37 次删除
  1. 1 0
      arch/h8300/Kconfig
  2. 1 1
      arch/h8300/kernel/Makefile
  3. 0 36
      arch/h8300/kernel/init_task.c

+ 1 - 0
arch/h8300/Kconfig

@@ -5,6 +5,7 @@ config H8300
 	select HAVE_GENERIC_HARDIRQS
 	select HAVE_GENERIC_HARDIRQS
 	select GENERIC_IRQ_SHOW
 	select GENERIC_IRQ_SHOW
 	select GENERIC_CPU_DEVICES
 	select GENERIC_CPU_DEVICES
+	select HAVE_GENERIC_INIT_TASK
 
 
 config SYMBOL_PREFIX
 config SYMBOL_PREFIX
 	string
 	string

+ 1 - 1
arch/h8300/kernel/Makefile

@@ -6,7 +6,7 @@ extra-y := vmlinux.lds
 
 
 obj-y := process.o traps.o ptrace.o irq.o \
 obj-y := process.o traps.o ptrace.o irq.o \
 	 sys_h8300.o time.o signal.o \
 	 sys_h8300.o time.o signal.o \
-         setup.o gpio.o init_task.o syscalls.o \
+         setup.o gpio.o syscalls.o \
 	 entry.o timer/
 	 entry.o timer/
 
 
 obj-$(CONFIG_MODULES) += module.o h8300_ksyms.o 
 obj-$(CONFIG_MODULES) += module.o h8300_ksyms.o 

+ 0 - 36
arch/h8300/kernel/init_task.c

@@ -1,36 +0,0 @@
-/*
- *  linux/arch/h8300/kernel/init_task.c
- */
-#include <linux/mm.h>
-#include <linux/module.h>
-#include <linux/sched.h>
-#include <linux/init.h>
-#include <linux/init_task.h>
-#include <linux/fs.h>
-#include <linux/mqueue.h>
-
-#include <asm/uaccess.h>
-#include <asm/pgtable.h>
-
-static struct signal_struct init_signals = INIT_SIGNALS(init_signals);
-static struct sighand_struct init_sighand = INIT_SIGHAND(init_sighand);
-/*
- * Initial task structure.
- *
- * All other task structs will be allocated on slabs in fork.c
- */
-__asm__(".align 4");
-struct task_struct init_task = INIT_TASK(init_task);
-
-EXPORT_SYMBOL(init_task);
-
-/*
- * Initial thread structure.
- *
- * We need to make sure that this is 8192-byte aligned due to the
- * way process stacks are handled. This is done by having a special
- * "init_task" linker map entry..
- */
-union thread_union init_thread_union __init_task_data =
-	{ INIT_THREAD_INFO(init_task) };
-