The patch titled Subject: mn10300: fix "pull clearing RESTORE_SIGMASK into block_sigmask()" fallout has been removed from the -mm tree. Its filename was mn10300-fix-pull-clearing-restore_sigmask-into-block_sigmask-fallout.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> Subject: mn10300: fix "pull clearing RESTORE_SIGMASK into block_sigmask()" fallout a610d6e672d6d3723e ("pull clearing RESTORE_SIGMASK into block_sigmask()") caused: arch/mn10300/kernel/signal.c: In function 'handle_signal': arch/mn10300/kernel/signal.c:462:3: warning: 'return' with no value, in function returning non-void [-Wreturn-type] Add the missing return values, and restore the indentation while we're at it. Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx> Cc: David Howells <dhowells@xxxxxxxxxx> Cc: Koichi Yasutake <yasutake.koichi@xxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- arch/mn10300/kernel/signal.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff -puN arch/mn10300/kernel/signal.c~mn10300-fix-pull-clearing-restore_sigmask-into-block_sigmask-fallout arch/mn10300/kernel/signal.c --- a/arch/mn10300/kernel/signal.c~mn10300-fix-pull-clearing-restore_sigmask-into-block_sigmask-fallout +++ a/arch/mn10300/kernel/signal.c @@ -459,10 +459,11 @@ static int handle_signal(int sig, else ret = setup_frame(sig, ka, oldset, regs); if (ret) - return; + return ret; signal_delivered(sig, info, ka, regs, - test_thread_flag(TIF_SINGLESTEP)); + test_thread_flag(TIF_SINGLESTEP)); + return 0; } /* _ Patches currently in -mm which might be from geert@xxxxxxxxxxxxxx are linux-next.patch mn10300-only-add-mmem-funcs-to-kbuild_cflags-if-gcc-supports-it.patch frv-kill-used-but-uninitialized-variable.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