From: Jan Willies <jan@willies.info>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/3] IBSS rate scaling fixes
Date: Wed, 03 Sep 2008 23:01:45 +0200 [thread overview]
Message-ID: <48BEFB39.7020308@willies.info> (raw)
In-Reply-To: <1220474540-16737-1-git-send-email-tomas.winkler@intel.com>
Tomas Winkler wrote:
> This series should fix fixed low rate (1Mbps) in IBSS. This is regression
> from 2.6.26
>
Thanks, I was just about to ask why my bitrate is fixed at 1Mbps. Will
this be going into 2.6.27?
- jan
prev parent reply other threads:[~2008-09-03 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 20:42 [PATCH 0/3] IBSS rate scaling fixes Tomas Winkler
2008-09-03 20:42 ` [PATCH 1/3] iwlwifi: rs - take a fresh set of supported rates at each cycle Tomas Winkler
2008-09-03 20:42 ` [PATCH 2/3] mac80211: Fix low bit rate in IBSS Tomas Winkler
2008-09-03 20:42 ` [PATCH 3/3] mac80211: Fix rate scale initialization " Tomas Winkler
2008-09-03 21:01 ` Jan Willies [this message]
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=48BEFB39.7020308@willies.info \
--to=jan@willies.info \
--cc=linux-wireless@vger.kernel.org \
--cc=tomas.winkler@intel.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).