From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
Cc: <linux-wireless@vger.kernel.org>, <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: allow the supported rate change by reassociate peer
Date: Tue, 11 Mar 2014 12:22:08 +0200 [thread overview]
Message-ID: <8738iphw6n.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1394013026-8426-1-git-send-email-yeohchunyeow@gmail.com> (Chun-Yeow Yeoh's message of "Wed, 5 Mar 2014 17:50:26 +0800")
Chun-Yeow Yeoh <yeohchunyeow@gmail.com> writes:
> IBSS mode requires the changing of supported rate. Do this
> by reassociate the peer. The investigation shows that if move
> from legacy to HT, the rate control won't work after changing
> the supported rate. But once changing the supported rate to HT,
> user can assign the TxRate in HT mode.
>
> Signed-off-by: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
Thanks, applied.
--
Kalle Valo
prev parent reply other threads:[~2014-03-11 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 9:50 [PATCH] ath10k: allow the supported rate change by reassociate peer Chun-Yeow Yeoh
2014-03-11 10:22 ` Kalle Valo [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=8738iphw6n.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yeohchunyeow@gmail.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).