linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: RFC:  Add precise timing to wifi association messages?
Date: Wed, 13 Nov 2013 19:18:36 +0100	[thread overview]
Message-ID: <1384366716.14578.13.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <5283BE63.8090801@candelatech.com> (sfid-20131113_190112_830842_FCA007A3)

On Wed, 2013-11-13 at 10:01 -0800, Ben Greear wrote:

> I chose a poor example here...my intention is to just add timers to existing
> messages...

What does this do that printk timestamps don't?

johannes


  reply	other threads:[~2013-11-13 18:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 17:58 RFC: Add precise timing to wifi association messages? Ben Greear
2013-11-13 18:01 ` Ben Greear
2013-11-13 18:18   ` Johannes Berg [this message]
2013-11-13 18:24     ` Ben Greear
2013-11-13 18:32       ` Johannes Berg
2013-11-13 18:39         ` Ben Greear

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=1384366716.14578.13.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@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).