From: Larry Finger <larry.finger@lwfinger.net>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Jiri Benc <jbenc@suse.cz>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH V3] mac80211: Add support for SIOCGIWRATE ioctl to provide rate information
Date: Thu, 10 May 2007 11:39:16 -0500 [thread overview]
Message-ID: <46434AB4.1070807@lwfinger.net> (raw)
In-Reply-To: <200705101156.12588.flamingice@sourmilk.net>
Michael Wu wrote:
> On Thursday 10 May 2007 10:56, Larry Finger wrote:
>> Why has the review of this patch been so strung out? Everything you comment
>> on here was in versions 1 & 2, but not mentioned in any review of those
>> versions.
>>
> Sorry, I've been busy. I'm pretty sure these issues are the last ones.
>
>> As to the usefulness of this function, I am testing in infrastructure, not
>> ad-hoc, mode, and the output matches the average rate in the log files if
>> debugging is enabled. If the address in u.sta.bssid is not correct, which
>> address should I be using? I still maintain that the user is entitled to
>> know the transmission rate from user space even if debugging is turned off,
>> and that this function is needed.
>>
> I didn't say infrastructure wasn't gonna work. That's the one that should
> work. However, adhoc probably won't.
Sorry, I misread your previous comment.
Why is txrate in the sta_info structure an int? I think it should be a small, positive integer.
Would it not be better as a u8, or a u16 if you think a larger range is needed?
Larry
>
> -Michael Wu
next prev parent reply other threads:[~2007-05-10 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 1:21 [PATCH V3] mac80211: Add support for SIOCGIWRATE ioctl to provide rate information Larry Finger
2007-05-04 10:58 ` Johannes Berg
2007-05-04 11:00 ` Jiri Benc
2007-05-04 11:07 ` Johannes Berg
2007-05-10 4:16 ` Michael Wu
2007-05-10 14:56 ` Larry Finger
2007-05-10 15:56 ` Michael Wu
2007-05-10 16:39 ` Larry Finger [this message]
2007-05-10 17:32 ` Michael Wu
2007-05-10 17:45 ` Larry Finger
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=46434AB4.1070807@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--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).