From: Daniel Mierswa <impulze@impulze.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Use nanosleep() instead of usleep()
Date: Wed, 19 Aug 2009 05:35:24 +0000 [thread overview]
Message-ID: <4A8B8F1C.90002@impulze.org> (raw)
In-Reply-To: <4A896729.3010302@impulze.org>
On 19.08.2009 04:17, Kay Sievers wrote:
> What's the point doing that wrapping? Will usleep() ever be removed from glibc?
Well POSIX.1-2008 removes the specification and if you disable
UCLIBC_SUSV3_LEGACY in uClibc (which is default) you will get undefined
references. I don't think it's too big of a problem to replace it for
the cases where the C library doesn't offer it, is it?
--
Mierswa, Daniel
If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
--- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22
next prev parent reply other threads:[~2009-08-19 5:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 14:20 [PATCH] Use nanosleep() instead of usleep() Daniel Mierswa
2009-08-18 0:22 ` Kay Sievers
2009-08-18 5:08 ` Daniel Mierswa
2009-08-19 2:17 ` Kay Sievers
2009-08-19 5:35 ` Daniel Mierswa [this message]
2009-08-24 16:41 ` Scott James Remnant
2009-08-24 17:23 ` Daniel Mierswa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A8B8F1C.90002@impulze.org \
--to=impulze@impulze.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).