* __set_current_state() suckage...
@ 2002-07-22 5:35 Rusty Russell
0 siblings, 0 replies; only message in thread
From: Rusty Russell @ 2002-07-22 5:35 UTC (permalink / raw)
To: linux-kernel; +Cc: torvalds
Should we rename __set_current_state to set_current_state, and put the
mb() inside add_wait_queue(), add_wait_queue_exclusive() and maybe
add_wait_queue_cond()?
People are getting confused by set_current_state() vs
__set_current_state(), esp. since it's only meaningful for
TASK_INTERRUPTIBLE/UNINTERRUPTIBLE.
Thoughts?
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-07-22 5:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-07-22 5:35 __set_current_state() suckage Rusty Russell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox