Re: trace/latency-hist: Consider new argument when probing the sched_switch tracer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Carsten Emde | 2016-01-05 10:21:59 [+0100]:

>Hi Thomas & Sebastian,
Hi Carsten,

>The sched_switch tracer has got a new argument. Fix the latency tracer
>accordingly.
>
>Thanks,
>    -Carsten.
>
>Signed-off-by: Carsten Emde <C.Emde@xxxxxxxxx>

Thanks.
Is it somehow possible to detect this kind of bugs at compile time? Is
there an easy way to do this?
What is blocking the latency-hist tracer from entering mainline?

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux