27 Apr, 2011
1 commit
-
In cases where a timerqueue_node or some structure that utilizes
a timerqueue_node is allocated on the stack, gcc would give warnings
caused by the timerqueue_init()'s calling RB_CLEAR_NODE, which
self-references the nodes uninitialized data.The solution is to create an rb_init_node() function that zeros
the rb_node structure out and then calls RB_CLEAR_NODE(), and
then call the new init function from timerqueue_init().CC: Thomas Gleixner
Acked-by: Arnd Bergmann
Signed-off-by: John Stultz
31 Mar, 2011
1 commit
-
Fixes generated by 'codespell' and manually reviewed.
Signed-off-by: Lucas De Marchi
11 Dec, 2010
2 commits
-
No point in calling a function just to dereference a pointer.
Signed-off-by: Thomas Gleixner
Cc: John Stultz -
Thomas pointed out a namespace collision between the new timerlist
infrastructure I introduced and the existing timer_list.cSo to avoid confusion, I've renamed the timerlist infrastructure
to timerqueue.Reported-by: Thomas Gleixner
Signed-off-by: John Stultz