> > Actually the hrsleep() function would allow for submillisecond sleeps, > which might be what some of the 450 users really want and they only use > msleep(1) because it's the next best thing. > A hrsleep() function is really what makes most sense from an API > perspective.
I respectfully disagree. The power of msleep is that the unit of sleep time is in the name; so in your proposal it would be hr_msleep or somesuch. I much rather do the opposite in that case; make the "short" name be the best implementation of the requested behavior, and have qualifiers for allowing exceptions to that... least surprise and all that. -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
