The patch titled Subject: kernel-watchdogc-print-traces-for-all-cpus-on-lockup-detection-fix-2 has been removed from the -mm tree. Its filename was kernel-watchdogc-print-traces-for-all-cpus-on-lockup-detection-fix-2.patch This patch was dropped because it was folded into kernel-watchdogc-print-traces-for-all-cpus-on-lockup-detection.patch ------------------------------------------------------ From: Jan Moskyto Matejka <mq@xxxxxxx> Subject: kernel-watchdogc-print-traces-for-all-cpus-on-lockup-detection-fix-2 This commit fixes this warning: kernel/watchdog.c: In function `watchdog_timer_fn': kernel/watchdog.c:368:4: warning: `smp_mb__after_clear_bit' is deprecated (declared at include/linux/bitops.h:48) [-Wdeprecated-declarations] smp_mb__after_clear_bit(); That code was introduced in commit 90e6b763ca8a5eb739e59489f42d45e13431d157 ("kernel/watchdog.c: print traces for all cpus on lockup detection") and then merged with another branch containing commit febdbfe8a91ce0d11939d4940b592eb0dba8d663 ("arch: Prepare for smp_mb__{before,after}_atomic()") which deprecates the smp_mb__after_clear_bit() call in favour of smp_mb__after_atomic(). Signed-off-by: Jan Moskyto Matejka <mq@xxxxxxx> Acked-by: Aaron Tomlin <atomlin@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- kernel/watchdog.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN kernel/watchdog.c~kernel-watchdogc-print-traces-for-all-cpus-on-lockup-detection-fix-2 kernel/watchdog.c --- a/kernel/watchdog.c~kernel-watchdogc-print-traces-for-all-cpus-on-lockup-detection-fix-2 +++ a/kernel/watchdog.c @@ -363,7 +363,7 @@ static enum hrtimer_restart watchdog_tim clear_bit(0, &soft_lockup_nmi_warn); /* Barrier to sync with other cpus */ - smp_mb__after_clear_bit(); + smp_mb__after_atomic(); } if (softlockup_panic) _ Patches currently in -mm which might be from mq@xxxxxxx are kernel-watchdogc-print-traces-for-all-cpus-on-lockup-detection.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