From: Kalle Valo <kvalo@codeaurora.org>
To: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Subject: Re: [PATCH 1/3] qtnfmac: handle channel switch events for connected stations only
Date: Fri, 26 Apr 2019 11:53:34 +0000 (UTC) [thread overview]
Message-ID: <20190426115334.B8F136028C@smtp.codeaurora.org> (raw)
In-Reply-To: <20190409073500.16402-2-sergey.matyukevich.os@quantenna.com>
Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> wrote:
> Channel switch events from firmware should be processed only when STA
> is already connected to BSS. On connect this notification is not needed
> since full BSS info will be supplied by cfg80211_connect_result.
>
> Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
3 patches applied to wireless-drivers-next.git, thanks.
4f87d486faf1 qtnfmac: handle channel switch events for connected stations only
888f1564a272 qtnfmac: allow to control DFS slave radar detection
0b68fe10b8e8 qtnfmac: modify debugfs to support multiple cards
--
https://patchwork.kernel.org/patch/10890667/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2019-04-26 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 7:35 [PATCH 0/3] qtnfmac: debugfs update and other misc fixes Sergey Matyukevich
2019-04-09 7:35 ` [PATCH 1/3] qtnfmac: handle channel switch events for connected stations only Sergey Matyukevich
2019-04-26 11:53 ` Kalle Valo [this message]
2019-04-09 7:35 ` [PATCH 2/3] qtnfmac: allow to control DFS slave radar detection Sergey Matyukevich
2019-04-09 7:35 ` [PATCH 3/3] qtnfmac: modify debugfs to support multiple cards Sergey Matyukevich
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=20190426115334.B8F136028C@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sergey.matyukevich.os@quantenna.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).