From: Felix Fietkau <nbd@openwrt.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH RFC] mac80211: change rate control API to allow multi-rate retry
Date: Tue, 30 Sep 2008 11:14:13 +0200 [thread overview]
Message-ID: <48E1EDE5.1070409@openwrt.org> (raw)
In-Reply-To: <1222759069.7064.52.camel@johannes.berg>
Johannes Berg wrote:
> If I'm counting correctly, that struct is now 2 bytes too large, you can
> cut out retry_limit I'd think by updating drivers to use
> retries[0].limit though. And iv/icv length can both be removed and added
> into the key_conf I think.
I'm still using retry_limit as maximum number of retries for the primary rate.
The retries[] array only specifies the settings for the alternate rates.
If it's only two bytes, then I'll just move over icv_len and iv_len.
- Felix
next prev parent reply other threads:[~2008-09-30 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 1:18 [PATCH RFC] mac80211: change rate control API to allow multi-rate retry Felix Fietkau
2008-09-30 7:17 ` Johannes Berg
2008-09-30 9:14 ` Felix Fietkau [this message]
2008-09-30 10:18 ` 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=48E1EDE5.1070409@openwrt.org \
--to=nbd@openwrt.org \
--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 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).