From: Vladimir Koutny <vlado@work.ksp.sk>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Michael Wu <flamingice@sourmilk.net>, Jiri Benc <jbenc@suse.cz>
Subject: Re: [PATCH] mac80211: configure default wmm params correctly
Date: Tue, 18 Mar 2008 14:45:06 +0100 [thread overview]
Message-ID: <47DFC762.10307@work.ksp.sk> (raw)
In-Reply-To: <1205846472.16475.46.camel@johannes.berg>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
>
> There is lots of trailing whitespace (use scripts/checkpatch.pl)
>
>> + if (local->hw.conf.channel->band == IEEE80211_BAND_2GHZ &&
>> + have_higher_than_11mbit)
>
> and that really needs to be indented differently.
>
Oops, sorry for that :(
>> + /* IBSS uses different parameters for Beacon sending */
>> + qparam.cw_min++;
>> + qparam.cw_min *= 2;
>> + qparam.cw_min--;
>> + local->ops->conf_tx(local_to_hw(local),
>> + IEEE80211_TX_QUEUE_BEACON, &qparam);
>
> And shouldn't we do that only for IBSS? I'm in favour of removing it
> completely, however, since the beacon queue is a way to construct
> hardware, not do things in software...
Good question; I've just moved this part of code out of
ieee80211_sta_set_ssid as that is not the best place for it. I don't
object to removing that code completely; seems that noone uses
IEEE80211_TX_QUEUE_BEACON anyway. On the other hand, it can be a good
hint for those implementing beaconing on hw where it has to be set
explicitly..
Vlado
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2008-03-18 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 12:48 [PATCH] mac80211: configure default wmm params correctly Vladimir Koutny
2008-03-18 13:21 ` Johannes Berg
2008-03-18 13:45 ` Vladimir Koutny [this message]
2008-03-18 14:16 ` Johannes Berg
2008-03-18 19:29 ` [PATCH v2] " Vladimir Koutny
2008-03-18 19:38 ` Johannes Berg
2008-03-18 20:14 ` Vladimir Koutny
2008-03-18 20:15 ` 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=47DFC762.10307@work.ksp.sk \
--to=vlado@work.ksp.sk \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).