Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <6ac56fa1-b369-831f-2b1d-9a188b7cbacc@quicinc.com>
Date:   Tue, 18 Jan 2022 10:43:15 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.4.1
Subject: Re: [PATCH] ath11k: set WMI_PEER_40MHZ while peer assoc for 6 GHz
Content-Language: en-US
To:     Kalle Valo <kvalo@kernel.org>
CC:     <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
References: <20220113023145.14292-1-quic_wgong@quicinc.com>
 <164242492251.16331.2627237965817574376.kvalo@kernel.org>
From:   Wen Gong <quic_wgong@quicinc.com>
In-Reply-To: <164242492251.16331.2627237965817574376.kvalo@kernel.org>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.