From: Saravana <saravanad@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: add debugfs file for current tx rate
Date: Thu, 29 Nov 2012 19:31:36 +0530 [thread overview]
Message-ID: <50B76AC0.3060507@posedge.com> (raw)
In-Reply-To: <1354197377.879.0.camel@jlt4.sipsolutions.net>
On 11/29/2012 07:26 PM, Johannes Berg wrote:
> On Thu, 2012-11-29 at 19:22 +0530, Saravana wrote:
>> Add a debugfs file showing the current tx rate.
>> The information available in the rc_stats file
>> doesn't evidently provides us the current tx rate.
>> This patch adds the support for the same.
>
> Applied. But it doesn't actually require the *rx* rework, so I've left
> that out.
>
*rx* rework is required for the last rx rate stat.
After giving my rationale on the need for addition of
last rx rate and mic failure count stat, i am waiting for
your inputs regarding the same.
> johannes
>
>
next prev parent reply other threads:[~2012-11-29 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 13:52 [PATCH v2] mac80211: add debugfs file for current tx rate Saravana
2012-11-29 13:56 ` Johannes Berg
2012-11-29 14:01 ` Saravana [this message]
2012-11-29 14:05 ` 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=50B76AC0.3060507@posedge.com \
--to=saravanad@posedge.com \
--cc=johannes@sipsolutions.net \
--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 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.