From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
xenomai@xenomai.org
Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : lib/cobalt: Provide RT-capable usleep
Date: Tue, 31 May 2016 13:06:23 +0200 [thread overview]
Message-ID: <574D702F.6000303@siemens.com> (raw)
In-Reply-To: <20160530152043.GE17483@hermes.click-hack.org>
On 2016-05-30 17:20, Gilles Chanteperdrix wrote:
> On Mon, May 30, 2016 at 04:39:42PM +0200, git repository hosting wrote:
>> Module: xenomai-jki
>> Branch: for-forge
>> Commit: ec9a8c81944d4a3e3f50af314fa58ade68dd28c2
>> URL: http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=ec9a8c81944d4a3e3f50af314fa58ade68dd28c2
>>
>> Author: Jan Kiszka <jan.kiszka@siemens.com>
>> Date: Mon May 30 14:58:07 2016 +0200
>>
>> lib/cobalt: Provide RT-capable usleep
>>
>> User may expect this (probably last) sleeping service to be available
>> under Cobalt just like sleep, nanosleep & Co.
>
> CONFORMING TO
> 4.3BSD, POSIX.1-2001. POSIX.1-2001 declares this function obsolete;
> use nanosleep(2) instead. POSIX.1-2008 removes the specification of
> usleep().
Do you expect people - and specifically Linux - to follow this soon?
The idea here is to reduce the level of surprise, and as long as using
usleep in your app doesn't cause an "undefined symbol" error, this risk
persists.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2016-05-31 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1b7OM2-0000oL-Q7@sd-51317.xenomai.org>
2016-05-30 15:20 ` [Xenomai] [Xenomai-git] Jan Kiszka : lib/cobalt: Provide RT-capable usleep Gilles Chanteperdrix
2016-05-31 11:06 ` Jan Kiszka [this message]
2016-05-31 11:32 ` Gilles Chanteperdrix
2016-05-31 12:18 ` Gilles Chanteperdrix
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=574D702F.6000303@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.