__set_current_state() suckage...

From: Rusty Russell (rusty@rustcorp.com.au)
Date: Mon Jul 22 2002 - 00:35:24 EST

Next message: Nicholas Miell: "Re: PATCH: 2.5.27 port thunderlan to the new DMA API"
Previous message: Andrew Morton: "Re: [PATCH][1/2] return values shrink_dcache_memory etc"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: Nicholas Miell: "Re: PATCH: 2.5.27 port thunderlan to the new DMA API"
Previous message: Andrew Morton: "Re: [PATCH][1/2] return values shrink_dcache_memory etc"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Jul 23 2002 - 22:00:37 EST