All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Sebastian Smolorz <Sebastian.Smolorz@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: Time representation in RTDM profiles
Date: Wed, 16 Aug 2006 16:26:41 +0200	[thread overview]
Message-ID: <44E32B21.8060508@domain.hid> (raw)
In-Reply-To: <200608161305.54411.Sebastian.Smolorz@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

Sebastian Smolorz wrote:
> Jan Kiszka wrote:
>> Sebastian Smolorz wrote:
>>> The possibility of redefinition was not the main goal here. As you
>>> mentioned it would be problematic. No, I introduced nanosecs_abs_t and
>>> nanosecs_rel_t because they are more intuitive and more "speaking" to the
>>> programmer. The meaning of a variable of such a type is clear at first
>>> sight.
>> Yeah, sounds reasonable to me. Then let's move these typedefs to rtdm.h
>> and document them as self-explanatory defines of the underlying standard
>> types, freezing their width and signedness at the same time.
> 
> Agreed.
> 
>> Actually, this would be useful for the driver API of RTDM as well.
> 
> That's right. No objections from my side.
> 

Done.

Though I checked things more then twice, some regression may be hidden,
specifically as I changed the signedness of timeout parameters of a few
RTDM driver API functions. All documented under
ksrc/skins/rtdm/API.CHANGES, and everyone is warned now.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2006-08-16 14:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16  8:49 [Xenomai-core] Time representation in RTDM profiles Jan Kiszka
2006-08-16 10:31 ` [Xenomai-core] " Sebastian Smolorz
2006-08-16 10:52   ` Jan Kiszka
2006-08-16 11:05     ` Sebastian Smolorz
2006-08-16 14:26       ` Jan Kiszka [this message]
2006-08-16 18:20         ` Sebastian Smolorz
2006-08-16 19:06           ` Jan Kiszka

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=44E32B21.8060508@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=Sebastian.Smolorz@domain.hid \
    --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.