From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from s3.sipsolutions.net ([144.76.43.152]:45204 "EHLO
	sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1756640Ab3KMSSk (ORCPT
	<rfc822;linux-wireless@vger.kernel.org>);
	Wed, 13 Nov 2013 13:18:40 -0500
Message-ID: <1384366716.14578.13.camel@jlt4.sipsolutions.net> (sfid-20131113_191843_686838_5BC6A4E8)
Subject: Re: RFC:  Add precise timing to wifi association messages?
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Date: Wed, 13 Nov 2013 19:18:36 +0100
In-Reply-To: <5283BE63.8090801@candelatech.com> (sfid-20131113_190112_830842_FCA007A3)
References: <5283BDB6.5020700@candelatech.com>
	 <5283BE63.8090801@candelatech.com> (sfid-20131113_190112_830842_FCA007A3)
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>

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