On Mon, Mar 24, 2014 at 8:11 PM, wrote:
> From: Dirk Brandewie
>
> Ensure that no timer callback is running since we are about to free
> the timer structure. We cannot guarantee that the call back is called
> on the CPU where the timer is running.
>
> Reported-by: Thomas Gleixner
>
On 03/24/2014 08:11 PM, dirk.brande...@gmail.com wrote:
> From: Dirk Brandewie
>
> Ensure that no timer callback is running since we are about to free
> the timer structure. We cannot guarantee that the call back is called
> on the CPU where the timer is running.
>
> Reported-by: Thomas
From: Dirk Brandewie
Ensure that no timer callback is running since we are about to free
the timer structure. We cannot guarantee that the call back is called
on the CPU where the timer is running.
Reported-by: Thomas Gleixner
Signed-off-by: Dirk Brandewie
Cc: Thomas Gleixner
Cc: "Rafael J.
From: Dirk Brandewie dirk.j.brande...@intel.com
Ensure that no timer callback is running since we are about to free
the timer structure. We cannot guarantee that the call back is called
on the CPU where the timer is running.
Reported-by: Thomas Gleixner t...@linutronix.de
Signed-off-by: Dirk
On 03/24/2014 08:11 PM, dirk.brande...@gmail.com wrote:
From: Dirk Brandewie dirk.j.brande...@intel.com
Ensure that no timer callback is running since we are about to free
the timer structure. We cannot guarantee that the call back is called
on the CPU where the timer is running.
On Mon, Mar 24, 2014 at 8:11 PM, dirk.brande...@gmail.com wrote:
From: Dirk Brandewie dirk.j.brande...@intel.com
Ensure that no timer callback is running since we are about to free
the timer structure. We cannot guarantee that the call back is called
on the CPU where the timer is running.
6 matches
Mail list logo