From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath9k_htc: configure bssid on ASSOC/IBSS change
Date: Wed, 20 Jun 2012 10:46:11 +0200 [thread overview]
Message-ID: <20120620084610.GA3579@redhat.com> (raw)
In-Reply-To: <1340172657-8699-1-git-send-email-rmanohar@qca.qualcomm.com>
On Wed, Jun 20, 2012 at 11:40:57AM +0530, Rajkumar Manoharan wrote:
> After the change "mac80211: remove spurious BSSID change flag",
> BSS_CHANGED_BSSID will not be passed on association or IBSS
> status changes. So it could be better to program bssid on ASSOC
> or IBSS change notification. Not doing so, is affecting the
> packet transmission.
>
> Reported-by: Michael Leun <lkml20120218@newton.leun.net>
> Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: stable@vger.kernel.org # 3.4 +
prev parent reply other threads:[~2012-06-20 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 6:10 [PATCH] ath9k_htc: configure bssid on ASSOC/IBSS change Rajkumar Manoharan
2012-06-20 8:46 ` Stanislaw Gruszka [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=20120620084610.GA3579@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rmanohar@qca.qualcomm.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).