From: Kalle Valo <kvalo@kernel.org>
To: Ma Ke <make_ruc2021@163.com>
Cc: quic_jjohnson@quicinc.com, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: ath12k: call ath12k_mac_fils_discovery() without condition
Date: Wed, 11 Oct 2023 11:55:41 +0300 [thread overview]
Message-ID: <87mswp4jxu.fsf@kernel.org> (raw)
In-Reply-To: <20231011072950.4097927-1-make_ruc2021@163.com> (Ma Ke's message of "Wed, 11 Oct 2023 15:29:50 +0800")
Ma Ke <make_ruc2021@163.com> writes:
> Mac80211 does not set flags BSS_CHANGED_FILS_DISCOVERY and
> BSS_CHANGED_UNSOL_BCAST_PROBE_RESP if there are no updates to
> FILS discovery and unsolicited broadcast probe response transmission
> configurations respectively. This results in the transmissions getting
> stopped during BSS change operations which do not include these
> attributes. Remove the checks for the flags and always send the existing
> configuration to firmware.
>
> Signed-off-by: Ma Ke <make_ruc2021@163.com>
This looks almost identical to Aloka's patch:
wifi: ath12k: call ath12k_mac_fils_discovery() without condition
https://git.kernel.org/netdev/net-next/c/43a10990404f
What's happening here?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath12k mailing list
ath12k@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/ath12k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Ma Ke <make_ruc2021@163.com>
Cc: quic_jjohnson@quicinc.com, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: ath12k: call ath12k_mac_fils_discovery() without condition
Date: Wed, 11 Oct 2023 11:55:41 +0300 [thread overview]
Message-ID: <87mswp4jxu.fsf@kernel.org> (raw)
In-Reply-To: <20231011072950.4097927-1-make_ruc2021@163.com> (Ma Ke's message of "Wed, 11 Oct 2023 15:29:50 +0800")
Ma Ke <make_ruc2021@163.com> writes:
> Mac80211 does not set flags BSS_CHANGED_FILS_DISCOVERY and
> BSS_CHANGED_UNSOL_BCAST_PROBE_RESP if there are no updates to
> FILS discovery and unsolicited broadcast probe response transmission
> configurations respectively. This results in the transmissions getting
> stopped during BSS change operations which do not include these
> attributes. Remove the checks for the flags and always send the existing
> configuration to firmware.
>
> Signed-off-by: Ma Ke <make_ruc2021@163.com>
This looks almost identical to Aloka's patch:
wifi: ath12k: call ath12k_mac_fils_discovery() without condition
https://git.kernel.org/netdev/net-next/c/43a10990404f
What's happening here?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-10-11 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 7:29 [PATCH] wifi: ath12k: call ath12k_mac_fils_discovery() without condition Ma Ke
2023-10-11 7:29 ` Ma Ke
2023-10-11 8:55 ` Kalle Valo [this message]
2023-10-11 8:55 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2023-09-05 17:43 Aloka Dixit
2023-09-05 20:11 ` Jeff Johnson
2023-09-28 15:10 ` 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=87mswp4jxu.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=make_ruc2021@163.com \
--cc=quic_jjohnson@quicinc.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 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.