From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] ath10k: send (re)assoc peer command when NSS changed
Date: Wed, 17 Dec 2014 12:32:45 +0200 [thread overview]
Message-ID: <87a92mr2gi.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1418719980-19753-2-git-send-email-janusz.dziedzic@tieto.com> (Janusz Dziedzic's message of "Tue, 16 Dec 2014 09:53:00 +0100")
Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
> Assoc peer command contain information about NSS.
> When we will get IEEE80211_RC_NSS_CHANGED we should
> also send (re) assoc peer command to be sure firmware
> will know about it and RC will work correctly.
>
> Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Does this fix a user visible bug or is this something you just found
from doing code review?
--
Kalle Valo
next prev parent reply other threads:[~2014-12-17 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 8:52 [PATCH 1/2] ath10k: fix low TX rates when IBSS and HT Janusz Dziedzic
2014-12-16 8:53 ` [PATCH 2/2] ath10k: send (re)assoc peer command when NSS changed Janusz Dziedzic
2014-12-17 10:32 ` Kalle Valo [this message]
2014-12-18 5:28 ` Janusz Dziedzic
2014-12-18 6:02 ` Kalle Valo
2014-12-16 11:10 ` [PATCH 1/2] ath10k: fix low TX rates when IBSS and HT Yeoh Chun-Yeow
2014-12-16 11:22 ` Janusz Dziedzic
2014-12-16 11:45 ` Janusz Dziedzic
2014-12-16 13:32 ` Yeoh Chun-Yeow
2014-12-17 3:56 ` Yeoh Chun-Yeow
2014-12-16 13:32 ` Yeoh Chun-Yeow
2014-12-23 15:23 ` Kalle Valo
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=87a92mr2gi.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=janusz.dziedzic@tieto.com \
--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).