From: Johannes Berg <johannes@sipsolutions.net>
To: Victor Goldenshtein <victorg@ti.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4] mac80211: add command to get current rssi
Date: Wed, 20 Jun 2012 10:15:49 +0200 [thread overview]
Message-ID: <1340180149.4655.23.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1340173975-13609-1-git-send-email-victorg@ti.com>
On Wed, 2012-06-20 at 09:32 +0300, Victor Goldenshtein wrote:
> + trace_drv_get_rssi(local, sdata);
> + ret = local->ops->get_rssi(&local->hw, &sdata->vif, sta, rssi_dbm);
> + trace_drv_return_int(local, ret);
Where are you tracing the sta?
And why not trace the value returned in *rssi_dbm?
johannes
next prev parent reply other threads:[~2012-06-20 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 6:32 [PATCH v4] mac80211: add command to get current rssi Victor Goldenshtein
2012-06-20 8:15 ` Johannes Berg [this message]
2012-06-20 13:22 ` Goldenshtein, Victor
2012-06-20 13:28 ` Johannes Berg
2012-06-20 15:14 ` Goldenshtein, Victor
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=1340180149.4655.23.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=victorg@ti.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).