On Sad, 2006-01-07 at 14:18 -0800, Pete Zaitcev wrote:
> Using wait_for_event is never an improvement. It's just a retarded API,
> which allows you to save lines-of-code count at expense of being opaque
> and conflicting with proper locking.
Used properly it makes things very clear. In particular lots of code
ends up with a function that figures out if it can make progress. Use
that function as the wait_event argument.
See the tty drivers which do this.
wait_event(tty_ldisc_wait, tty_ldisc_try(tty));
is pretty explicit.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
