From: Rameshkumar Sundaram <quic_ramess@quicinc.com>
To: <johannes@sipsolutions.net>, <ath11k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>,
Rameshkumar Sundaram <quic_ramess@quicinc.com>
Subject: [PATCH v3 0/3] wifi: Add support to enable/disable bss color collision detection
Date: Wed, 1 Feb 2023 12:26:35 +0530 [thread overview]
Message-ID: <20230201065638.25990-1-quic_ramess@quicinc.com> (raw)
This patchset adds configuration option to Enable/Disable 802.11ax BSS
color collision detection.
Changes since v2:
- Updated wifi prefix
Changes since v1:
- Split nl80211 patch(patch 1/2 on v1) to two patches.
Rameshkumar Sundaram (3):
wifi: cfg80211: add support to enable/disable bss color collision
detection
wifi: mac80211: Avoid BSS color collision detection if its disabled
wifi: ath11k: add support to enable/disable BSS color collision
detection
drivers/net/wireless/ath/ath11k/mac.c | 5 ++++-
include/net/cfg80211.h | 2 ++
include/uapi/linux/nl80211.h | 3 +++
net/mac80211/rx.c | 3 ++-
net/wireless/nl80211.c | 3 +++
5 files changed, 14 insertions(+), 2 deletions(-)
base-commit: 4ca69027691a0039279b64cfa0aa511d9c9fde59
--
2.17.1
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next reply other threads:[~2023-02-01 6:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 6:56 Rameshkumar Sundaram [this message]
2023-02-01 6:56 ` [PATCH v3 1/3] wifi: cfg80211: add support to enable/disable bss color collision detection Rameshkumar Sundaram
2023-02-15 17:34 ` Johannes Berg
2023-02-01 6:56 ` [PATCH v3 2/3] wifi: mac80211: Avoid BSS color collision detection if its disabled Rameshkumar Sundaram
2023-02-15 17:35 ` Johannes Berg
2023-02-15 17:37 ` Johannes Berg
2023-02-01 6:56 ` [PATCH v3 3/3] wifi: ath11k: add support to enable/disable BSS color collision detection Rameshkumar Sundaram
2023-02-15 17:37 ` Johannes Berg
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=20230201065638.25990-1-quic_ramess@quicinc.com \
--to=quic_ramess@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--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).