The patch titled kernel/sched.c: remove double unlikely has been added to the -mm tree. Its filename is kernel-schedc-remove-double-unlikely.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: kernel/sched.c: remove double unlikely From: Roel Kluin <12o3l@xxxxxxxxxx> Combine two unlikely's Signed-off-by: Roel Kluin <12o3l@xxxxxxxxxx> Cc: Ingo Molnar <mingo@xxxxxxx> Cc: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- kernel/sched.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN kernel/sched.c~kernel-schedc-remove-double-unlikely kernel/sched.c --- a/kernel/sched.c~kernel-schedc-remove-double-unlikely +++ a/kernel/sched.c @@ -3959,7 +3959,7 @@ need_resched_nonpreemptible: if (prev->state && !(preempt_count() & PREEMPT_ACTIVE)) { if (unlikely((prev->state & TASK_INTERRUPTIBLE) && - unlikely(signal_pending(prev)))) { + signal_pending(prev))) { prev->state = TASK_RUNNING; } else { deactivate_task(rq, prev, 1); _ Patches currently in -mm which might be from 12o3l@xxxxxxxxxx are git-dvb.patch adt746x-logical-bitwise-confusion-in-set_max_duty_at_crit.patch kernel-schedc-remove-double-unlikely.patch block-blk-mergec-inverted-likeliness-in-ll_back_merge_fn.patch free-when-fb-cant-be-registered-in-video-aty-atyfb_basec.patch drivers-video-aty-aty128fbc-fix-incorrect-usage-of-strncat-in-aty128_init.patch drivers-video-imsttfbc-add-missing-curly-brackets.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