[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9df5fa10810170605t50e366e9nf62f8a18df37fc3c@mail.gmail.com>
Date: Fri, 17 Oct 2008 19:05:32 +0600
From: "Rakib Mullick" <rakib.mullick@...il.com>
To: linux-kernel@...r.kernel.org
Cc: "Ingo Molnar" <mingo@...e.hu>,
"Andrew Morton" <akpm@...ux-foundation.org>
Subject: [PATCH] init: Properly placing noinline keyword.
Here, noinline keyword should be placed between storage class and type.
Thanks.
Signed-off-by: Md.Rakib H. Mullick(rakib.mullick@...il.com)
--- linux-2.6-stable.orig/init/main.c 2008-10-16 20:04:15.000000000 +0600
+++ linux-2.6-stable/init/main.c 2008-10-16 20:59:29.562096784 +0600
@@ -457,7 +457,7 @@ static void __init setup_command_line(ch
* gcc-3.4 accidentally inlines this function, so use noinline.
*/
-static void noinline __init_refok rest_init(void)
+static noinline void __init_refok rest_init(void)
__releases(kernel_lock)
{
int pid;
@@ -792,7 +792,7 @@ static void run_init_process(char *init_
/* This is a non __init function. Force it to be noinline otherwise gcc
* makes it inline to init() and it becomes part of init.text section
*/
-static int noinline init_post(void)
+static noinline int init_post(void)
{
free_initmem();
unlock_kernel();
--
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