From: Kalle Valo <kvalo@codeaurora.org>
To: John Crispin <john@phrozen.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [PATCH V3 3/4] ath11k: add WMI calls required for handling BSS color
Date: Tue, 17 Mar 2020 06:45:00 +0000 (UTC) [thread overview]
Message-ID: <20200317064500.9F973C433BA@smtp.codeaurora.org> (raw)
In-Reply-To: <20191217141921.8114-3-john@phrozen.org>
John Crispin <john@phrozen.org> wrote:
> If the he_operation field of the beacon sets a BSS color, we need to inform
> the FW of the settings. This patch adds the WMI command handlers required
> to do so.
>
> Signed-off-by: John Crispin <john@phrozen.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
2 patches applied to ath-next branch of ath.git, thanks.
5a032c8d1953 ath11k: add WMI calls required for handling BSS color
beb2f77297b0 ath11k: add handling for BSS color
--
https://patchwork.kernel.org/patch/11297707/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-03-17 6:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 14:19 [PATCH V3 1/4] nl80211: add handling for BSS color John Crispin
2019-12-17 14:19 ` John Crispin
2019-12-17 14:19 ` [PATCH V3 2/4] mac80211: " John Crispin
2019-12-17 14:19 ` John Crispin
2019-12-17 14:19 ` [PATCH V3 3/4] ath11k: add WMI calls required for handling " John Crispin
2019-12-17 14:19 ` John Crispin
2020-03-16 6:19 ` Kalle Valo
2020-03-16 6:19 ` Kalle Valo
2020-03-17 6:45 ` Kalle Valo
2020-03-17 6:45 ` Kalle Valo [this message]
2019-12-17 14:19 ` [PATCH V3 4/4] ath11k: add handling for " John Crispin
2019-12-17 14:19 ` John Crispin
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=20200317064500.9F973C433BA@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=john@phrozen.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.