From: Kalle Valo <kalle.valo@nokia.com>
To: "Luis R. Rodriguez" <mcgrof@winlab.rutgers.edu>
Cc: "bruno randolf" <br1@einfach.org>, linux-wireless@vger.kernel.org
Subject: Re: [ath5k-devel] [PATCH 2/4] ath5k: always extend rx timestamp with tsf
Date: Mon, 21 Jan 2008 08:32:48 +0200 [thread overview]
Message-ID: <87tzl7g033.fsf@nokia.com> (raw)
In-Reply-To: <43e72e890801200046n2c858c97k3506664431b937e6@mail.gmail.com> (ext Luis R. Rodriguez's message of "Sun\, 20 Jan 2008 03\:46\:05 -0500")
Luis R. Rodriguez <mcgrof@winlab.rutgers.edu> writes:
>> what i mean
>> is 32768us equals about 32ms. i'll remove that dot to make it unambigous.
>
> Yeah thanks, might be more clear for those of us not used to that
> convention, I didn't even know it existed. Where is this "." for 1000
> notation convention used, just so I know :) ?
It seems most of Europe uses it, even though we Finns don't:
"In much of Europe, however, a comma is used as a decimal separator,
while a full stop or a space is used for the presentation of large
numbers:
* 1.000.000 (One million)
* 1.000,000 or 1 000,000 (One thousand)"
http://en.wikipedia.org/wiki/Full_stop#Mathematical_usage
--
Kalle Valo
next prev parent reply other threads:[~2008-01-21 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 5:37 [ath5k-devel] [PATCH 2/4] ath5k: always extend rx timestamp with tsf bruno randolf
2008-01-20 8:46 ` Luis R. Rodriguez
2008-01-21 6:32 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-20 9:53 bruno randolf
2008-01-20 9:57 ` Jiri Slaby
2008-01-18 12:50 [PATCH 1/4] ath5k: debug level improvements Bruno Randolf
2008-01-18 12:50 ` [PATCH 2/4] ath5k: always extend rx timestamp with tsf Bruno Randolf
2008-01-19 22:20 ` Luis R. Rodriguez
2008-01-20 2:12 ` [ath5k-devel] " Derek Smithies
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=87tzl7g033.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=br1@einfach.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@winlab.rutgers.edu \
/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).