The patch titled init: properly placing noinline keyword has been removed from the -mm tree. Its filename was init-properly-placing-noinline-keyword.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: init: properly placing noinline keyword From: "Rakib Mullick" <rakib.mullick@xxxxxxxxx> checkpatch warns about 'static void noinline'. It wants `static noinline void'. Both are permissible, but the kernel consistently uses `static inline' and `static noinline', and consistency is good. Hence let's keep the checkpatch warning and fix up this code site. [akpm@xxxxxxxxxxxxxxxxxxxx: rewrote changelog] Signed-off-by: Md.Rakib H. Mullick <rakib.mullick@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- init/main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff -puN init/main.c~init-properly-placing-noinline-keyword init/main.c --- a/init/main.c~init-properly-placing-noinline-keyword +++ a/init/main.c @@ -447,7 +447,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; @@ -786,7 +786,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(); _ Patches currently in -mm which might be from rakib.mullick@xxxxxxxxx are origin.patch linux-next.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html