Subject: [merged] idle-remove-cpu_idle-forward-declarations.patch removed from -mm tree To: geert+renesas@xxxxxxxxx,tglx@xxxxxxxxxxxxx,mm-commits@xxxxxxxxxxxxxxx From: akpm@xxxxxxxxxxxxxxxxxxxx Date: Mon, 09 Jun 2014 12:41:46 -0700 The patch titled Subject: idle: remove cpu_idle() forward declarations has been removed from the -mm tree. Its filename was idle-remove-cpu_idle-forward-declarations.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> Subject: idle: remove cpu_idle() forward declarations After all architectures were converted to the generic idle framework, d190e8195b90 ("idle: Remove GENERIC_IDLE_LOOP config switch") removed the last caller of cpu_idle(). The forward declarations in header files were forgotten. Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- include/linux/cpu.h | 1 - include/linux/smp.h | 2 -- 2 files changed, 3 deletions(-) diff -puN include/linux/cpu.h~idle-remove-cpu_idle-forward-declarations include/linux/cpu.h --- a/include/linux/cpu.h~idle-remove-cpu_idle-forward-declarations +++ a/include/linux/cpu.h @@ -256,7 +256,6 @@ enum cpuhp_state { }; void cpu_startup_entry(enum cpuhp_state state); -void cpu_idle(void); void cpu_idle_poll_ctrl(bool enable); diff -puN include/linux/smp.h~idle-remove-cpu_idle-forward-declarations include/linux/smp.h --- a/include/linux/smp.h~idle-remove-cpu_idle-forward-declarations +++ a/include/linux/smp.h @@ -13,8 +13,6 @@ #include <linux/init.h> #include <linux/llist.h> -extern void cpu_idle(void); - typedef void (*smp_call_func_t)(void *info); struct call_single_data { struct llist_node llist; _ Patches currently in -mm which might be from geert+renesas@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