From: Kalle Valo <kvalo@kernel.org>
To: Wen Gong <quic_wgong@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath11k: set WMI_PEER_40MHZ while peer assoc for 6 GHz
Date: Tue, 18 Jan 2022 08:33:14 +0200 [thread overview]
Message-ID: <877daximdx.fsf@kernel.org> (raw)
In-Reply-To: <6ac56fa1-b369-831f-2b1d-9a188b7cbacc@quicinc.com> (Wen Gong's message of "Tue, 18 Jan 2022 10:43:15 +0800")
Wen Gong <quic_wgong@quicinc.com> writes:
> On 1/17/2022 9:08 PM, Kalle Valo wrote:
>> Wen Gong <quic_wgong@quicinc.com> wrote:
>>
>>> When station connect to AP of 6 GHz with 40 MHz bandwidth, the TX is
>>> always stay 20 MHz, it is because the flag WMI_PEER_40MHZ is not set
>>> while peer assoc. Add the flag if remote peer is 40 MHz bandwidth.
>>>
>>> Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-02892.1-QCAHSPSWPL_V1_V2_SILICONZ_LITE-1
>> Fixes tag
>>
>> Fixes: 2cdf2b3cdf54 ("ath11k: add 6ghz params in peer assoc command")
>>
>> has these problem(s):
>>
>> - Target SHA1 does not exist
>>
>> Did you mean:
>>
>> Fixes: c3a7d7eb4c98 ("ath11k: add 6 GHz params in peer assoc command")
>
> Thanks.
>
> yes, it is.
>
> I see you have already changed it in master-pending.
Yeah, so no need to resend because of this.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2022-01-18 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 2:31 [PATCH] ath11k: set WMI_PEER_40MHZ while peer assoc for 6 GHz Wen Gong
2022-01-17 13:08 ` Kalle Valo
2022-01-18 2:43 ` Wen Gong
2022-01-18 6:33 ` Kalle Valo [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=877daximdx.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_wgong@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 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).