All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: bruno randolf <br1@einfach.org>
Cc: "Luis R. Rodriguez" <mcgrof@winlab.rutgers.edu>,
	"" <derek@indranet.co.nz>, Michael Wu <flamingice@sourmilk.net>,
	ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
	linville@tuxdriver.com, Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [ath5k-devel] [PATCH 2/4] ath5k: always extend rx timestamp with tsf
Date: Sun, 20 Jan 2008 10:57:17 +0100	[thread overview]
Message-ID: <47931AFD.1000903@gmail.com> (raw)
In-Reply-To: <45504.61.115.136.26.1200822830.squirrel@webmail.einfach.org>

On 01/20/2008 10:53 AM, bruno randolf wrote:
> On Sunday 20 January 2008 17:46:05 Luis R. Rodriguez wrote:
>> 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 :) ?
> 
> in german speaking countries at least (i am austrian), don't really know
> where else...

In Czechia too (few (hundreds) km northern/eastern). So central europe, at least ;).

  reply	other threads:[~2008-01-20  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-20  9:53 [ath5k-devel] [PATCH 2/4] ath5k: always extend rx timestamp with tsf bruno randolf
2008-01-20  9:57 ` Jiri Slaby [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-20  5:37 bruno randolf
2008-01-20  8:46 ` Luis R. Rodriguez
2008-01-21  6:32   ` Kalle Valo
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=47931AFD.1000903@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=br1@einfach.org \
    --cc=derek@indranet.co.nz \
    --cc=flamingice@sourmilk.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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 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.