The patch titled pps: remove unreachable code has been added to the -mm tree. Its filename is pps-remove-unreachable-code.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://userweb.kernel.org/~akpm/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: pps: remove unreachable code From: Alexander Gordeev <lasaine@xxxxxxxxxxxxx> Remove code enabled only when CONFIG_PREEMPT_RT is turned on because it is not used in the vanilla kernel. Signed-off-by: Alexander Gordeev <lasaine@xxxxxxxxxxxxx> Cc: john stultz <johnstul@xxxxxxxxxx> Cc: Rodolfo Giometti <giometti@xxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/pps/generators/pps_gen_parport.c | 5 ----- 1 file changed, 5 deletions(-) diff -puN drivers/pps/generators/pps_gen_parport.c~pps-remove-unreachable-code drivers/pps/generators/pps_gen_parport.c --- a/drivers/pps/generators/pps_gen_parport.c~pps-remove-unreachable-code +++ a/drivers/pps/generators/pps_gen_parport.c @@ -216,11 +216,6 @@ static void parport_attach(struct parpor hrtimer_init(&device.timer, CLOCK_REALTIME, HRTIMER_MODE_ABS); device.timer.function = hrtimer_event; -#ifdef CONFIG_PREEMPT_RT - /* hrtimer interrupt will run in the interrupt context with this */ - device.timer.irqsafe = 1; -#endif - hrtimer_start(&device.timer, next_intr_time(&device), HRTIMER_MODE_ABS); return; _ Patches currently in -mm which might be from lasaine@xxxxxxxxxxxxx are pps-initialize-ts_real-properly.patch pps-make-pps_gen_parport-depend-on-broken.patch pps-remove-unreachable-code.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