On 01/14, Davidlohr Bueso wrote:
>
> Call __set_current_state() instead of assigning the new state directly.
> These interfaces also aid CONFIG_DEBUG_ATOMIC_SLEEP environments, keeping
> track of who changed the state.
Acked-by: Oleg Nesterov
> Signed-off-by: Davidlohr Bueso
> Cc: Oleg
On 01/14, Davidlohr Bueso wrote:
Call __set_current_state() instead of assigning the new state directly.
These interfaces also aid CONFIG_DEBUG_ATOMIC_SLEEP environments, keeping
track of who changed the state.
Acked-by: Oleg Nesterov o...@redhat.com
Signed-off-by: Davidlohr Bueso
Call __set_current_state() instead of assigning the new state directly.
These interfaces also aid CONFIG_DEBUG_ATOMIC_SLEEP environments, keeping
track of who changed the state.
Signed-off-by: Davidlohr Bueso
Cc: Oleg Nesterov
---
kernel/signal.c | 4 ++--
1 file changed, 2 insertions(+), 2
Call __set_current_state() instead of assigning the new state directly.
These interfaces also aid CONFIG_DEBUG_ATOMIC_SLEEP environments, keeping
track of who changed the state.
Signed-off-by: Davidlohr Bueso dbu...@suse.de
Cc: Oleg Nesterov o...@redhat.com
---
kernel/signal.c | 4 ++--
1 file
4 matches
Mail list logo