From: Wen Gong <quic_wgong@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
<ath11k@lists.infradead.org>
Subject: Re: [PATCH] wifi: mac80211: RCU-ify link STA pointers
Date: Tue, 13 Sep 2022 12:29:44 +0800 [thread overview]
Message-ID: <c28b9240-c45e-c8cd-ece7-d967da93896c@quicinc.com> (raw)
In-Reply-To: <875yhs97kg.fsf@kernel.org>
Please ignore this mail which is not really for patch review.
On 9/12/2022 7:05 PM, Kalle Valo wrote:
> Wen Gong <quic_wgong@quicinc.com> writes:
>
>> On 9/12/2022 6:49 PM, Kalle Valo wrote:
>>> Wen Gong <quic_wgong@quicinc.com> writes:
>>>
>>>> Hi Johannes,
>>>>
>>>> Currently for MLO test, the others links's rx_nss of struct
>>>> ieee80211_link_sta is still value 0 in ieee80211_set_associated(),
>>>> becaue they are not pass into ieee80211_sta_set_rx_nss() in
>>>> mac80211 except the deflink which means the primary link.
>>>> This lead driver get nss = 0 for other links. Will you fix it
>>>> or is it design by default?
>>>>
>>>> Only primary link has valid rx_nss value which is not 0 by below call stack.
>>>> ieee80211_assoc_success()->
>>>> rate_control_rate_init(sta);
>>>>
>>>> commit:c71420db653aba30a234d1e4cf86dde376e604fa
>>>> wifi: mac80211: RCU-ify link STA pointers
>>> Strange format and s-o-b missing. Was this meant as an RFC patch?
>> This is not a patch for review, it is to ask some question about the patch
>>
>> "wifi: mac80211: RCU-ify link STA pointers" which is already upstream.
> Then you should not add "[PATCH]" in the subject. The string "[PATCH]"
> is supposed to inform that the email contains a patch which should be
> applied.
>
prev parent reply other threads:[~2022-09-13 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 9:36 [PATCH] wifi: mac80211: RCU-ify link STA pointers Wen Gong
2022-09-12 10:49 ` Kalle Valo
2022-09-12 10:55 ` Wen Gong
2022-09-12 11:05 ` Kalle Valo
2022-09-13 4:29 ` Wen Gong [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=c28b9240-c45e-c8cd-ece7-d967da93896c@quicinc.com \
--to=quic_wgong@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox