moz@compsoc.man.ac.uk said:
> So it seems to be a bug at least in terms of timing. Unfortunately I
> only got about 4 replies to the patches that touched 20+ drivers. I
> suppose I should just hassle maintainers until they fix it or tell me
> where I've gone wrong ...
Actually, I was quite happy calling schedule_timeout in the flash drivers
without changing current->state. I'm waiting to something to happen, and
just to be considerate, I'm asking to be put to sleep for the 'expected'
amount of time for whatever's happening. If there's other stuff on the run
queue, it won't return immediately, will it? If there isn't other stuff on
the run queue, I'll just busy wait till the flash chip's finished.
Otherwise, it would be TASK_UNINTERRUPTIBLE.
-- dwmw2- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Sep 07 2000 - 21:00:29 EST