From: Johannes Berg <johannes@sipsolutions.net>
To: Rohan Joyce <rojoyce.github@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] nl80211: add NL80211_CMD_GET_TSF
Date: Mon, 23 Feb 2015 15:31:20 +0100 [thread overview]
Message-ID: <1424701880.3075.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1424699832-19284-2-git-send-email-rojoyce.github@gmail.com> (sfid-20150223_151201_815020_CABEA63C)
On Mon, 2015-02-23 at 21:57 +0800, Rohan Joyce wrote:
> This patch adds a command NL80211_CMD_GET_TSF that retrieves the 64 bit time
> synchronisation value for an interface. It returns the value in a uint64
> attribute of type NL80211_ATTR_TSF.
This should explain why and how this could possibly be used - I don't
see any reasonable usage since the TSF is quickly changing and this API
doesn't really allow for any synchronisation.
johannes
next prev parent reply other threads:[~2015-02-23 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 13:57 [PATCH 0/1] nl80211: add NL80211_CMD_GET_TSF Rohan Joyce
2015-02-23 13:57 ` [PATCH 1/1] " Rohan Joyce
2015-02-23 14:31 ` Johannes Berg [this message]
2015-02-23 15:38 ` Rohan Joyce
2015-02-24 20:11 ` Johannes Berg
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=1424701880.3075.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rojoyce.github@gmail.com \
/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).