public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: <ath11k@lists.infradead.org>,  <linux-wireless@vger.kernel.org>,
	<regressions@lists.linux.dev>
Subject: Re: [PATCH v2] wifi: ath11k: move power type check to ASSOC stage when connecting to 6 GHz AP
Date: Tue, 21 May 2024 08:12:05 +0300	[thread overview]
Message-ID: <878r03eoka.fsf@kernel.org> (raw)
In-Reply-To: <b6b23a29-78ef-4e4f-8042-e13833fcb1ec@quicinc.com> (Baochen Qiang's message of "Tue, 21 May 2024 09:52:06 +0800")

Baochen Qiang <quic_bqiang@quicinc.com> writes:

> On 5/20/2024 11:34 PM, Kalle Valo wrote:
>> Baochen Qiang <quic_bqiang@quicinc.com> writes:
>>> On 5/11/2024 5:54 PM, Kalle Valo wrote:
>>>
>>>> Oh, this fell through the cracks. Commit bc8a0fac8677 was introduced in
>>>> v6.9-rc1 so I should have sent this to v6.9 but it's too late now. I'll
>>>> need to queue this for v6.10 via wireless tree.
>>>>
>>>> Adding the regression also to regzbot:
>>>>
>>>> #regzbot introduced: bc8a0fac8677
>>>> #regzbot title: ath11k: connection to 6 GHz AP fails
>>>>
>>> Hi Kalle, with an upcoming patch this regression is expected to be fixed:
>>>
>>> https://lore.kernel.org/all/20240506214536.310434f55f76.I6aca291ee06265e3f63e0f9024ba19a850b53a33@changeid/#t
>>>
>>> So here the ath11k fix would not be needed any more once above patch got merged.
>> 
>> What happens if we apply both patch 'wifi: ath11k: move power type check
>> to ASSOC stage when connecting to 6 GHz AP' and patchset 'wifi:
>> mac80211: build TPE handling'? In other words, do they conflict from
>> functionality point of view?
>
> No functional conflict, 6 GHz AP connection would also succeed with
> both of them applied.

Ok, thanks. In that case I would like take patch 'wifi: ath11k: move
power type check to ASSOC stage when connecting to 6 GHz AP' to
ath-current branch from which it will go to v6.10. Is that ok for
everyone?

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2024-05-21  5:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24  6:40 [PATCH v2] wifi: ath11k: move power type check to ASSOC stage when connecting to 6 GHz AP Baochen Qiang
2024-04-24 12:20 ` Kalle Valo
2024-04-24 19:21 ` Jeff Johnson
2024-05-11  9:54 ` Kalle Valo
2024-05-16 11:42   ` Linux regression tracking (Thorsten Leemhuis)
2024-05-17  2:14   ` Baochen Qiang
2024-05-17  5:58     ` Linux regression tracking (Thorsten Leemhuis)
2024-05-20 15:34     ` Kalle Valo
2024-05-21  1:52       ` Baochen Qiang
2024-05-21  5:12         ` Kalle Valo [this message]
2024-05-21  5:27           ` Baochen Qiang
2024-05-21 16:27             ` Jeff Johnson
2024-05-23 12:48 ` 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=878r03eoka.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_bqiang@quicinc.com \
    --cc=regressions@lists.linux.dev \
    /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