From: "Yu Zhang (Yuriy)" <quic_yuzha@quicinc.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: <ath11k@lists.infradead.org>, <jjohnson@kernel.org>,
<kvalo@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-wireless@vger.kernel.org>, <quic_cjhuang@quicinc.com>,
<vbenes@redhat.com>
Subject: Re: [PATCH] wifi: ath11k: allow APs combination when dual stations are supported
Date: Wed, 2 Apr 2025 20:23:23 +0800 [thread overview]
Message-ID: <1eb3933d-9aac-4e47-a7a5-818aa18b137a@quicinc.com> (raw)
In-Reply-To: <748a5a75-1385-4691-85c1-e9cc5eb4ffc2@oss.qualcomm.com>
On 1/16/2025 8:31 AM, Jeff Johnson wrote:
> On 1/15/2025 5:03 AM, Jose Ignacio Tornos Martinez wrote:
>> Hello Yuriy,
>>
>> Thank you for the information.
>> My platform, as you said, is just wcn6855 hw2.1, but using NetworkManager
>> with the default configuration.
>> If this is the only stopper, you can skip and not consider as a wrong case,
>> because (sorry for repeating) it is just a matter of the number of available
>> resources that can be adjusted after some research from us.
>>
>> Thanks
>>
>> Best regards
>> Jose Ignacio
>
> Thanks,
>
> I was hesitant to take Yuriv's patch since your problem was not fixed. But I
> guess you are already broken with the current code, so I'll take his patch,
> and then we can work on fixing any other issues from there.
>
> Kalle, can you review? You currently have this deferred in patchwork:
> https://patchwork.kernel.org/project/linux-wireless/patch/20240829064420.3074140-1-quic_yuzha@quicinc.com/
>
> /jeff
>
Jeff
Could you help it?
Thanks,
Yuriy
next prev parent reply other threads:[~2025-04-02 12:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 9:18 Jose Ignacio Tornos Martinez
2024-12-03 1:54 ` Yu Zhang (Yuriy)
2024-12-03 8:04 ` Jose Ignacio Tornos Martinez
2024-12-03 8:28 ` Yu Zhang (Yuriy)
2024-12-03 9:48 ` Jose Ignacio Tornos Martinez
2024-12-03 10:48 ` Yu Zhang (Yuriy)
2024-12-03 16:33 ` Jose Ignacio Tornos Martinez
2024-12-04 3:21 ` Yu Zhang (Yuriy)
2024-12-04 7:51 ` Jose Ignacio Tornos Martinez
2024-12-04 8:30 ` Jose Ignacio Tornos Martinez
2024-12-04 9:18 ` Yu Zhang (Yuriy)
2024-12-05 11:07 ` Jose Ignacio Tornos Martinez
2024-12-06 2:24 ` Yu Zhang (Yuriy)
2024-12-08 12:13 ` Jose Ignacio Tornos Martinez
2024-12-09 2:29 ` Yu Zhang (Yuriy)
2024-12-09 8:03 ` Jose Ignacio Tornos Martinez
2024-12-09 8:33 ` Yu Zhang (Yuriy)
2024-12-10 8:44 ` Jose Ignacio Tornos Martinez
2024-12-11 2:10 ` Yu Zhang (Yuriy)
2024-12-11 17:41 ` Jose Ignacio Tornos Martinez
2025-01-14 18:34 ` Jose Ignacio Tornos Martinez
2025-01-15 8:59 ` Yu Zhang (Yuriy)
2025-01-15 9:46 ` Jose Ignacio Tornos Martinez
2025-01-15 10:48 ` Yu Zhang (Yuriy)
2025-01-15 11:06 ` Jose Ignacio Tornos Martinez
2025-01-15 11:20 ` Yu Zhang (Yuriy)
2025-01-15 11:55 ` Jose Ignacio Tornos Martinez
2025-01-15 12:04 ` Yu Zhang (Yuriy)
2025-01-15 13:03 ` Jose Ignacio Tornos Martinez
2025-01-16 0:31 ` Jeff Johnson
2025-02-06 7:46 ` Yu Zhang (Yuriy)
2025-02-06 20:20 ` Jeff Johnson
2025-02-07 2:01 ` Yu Zhang (Yuriy)
2025-04-02 12:23 ` Yu Zhang (Yuriy) [this message]
2024-12-09 11:23 ` Janusz Dziedzic
2024-12-10 2:32 ` Yu Zhang (Yuriy)
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=1eb3933d-9aac-4e47-a7a5-818aa18b137a@quicinc.com \
--to=quic_yuzha@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_cjhuang@quicinc.com \
--cc=vbenes@redhat.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
all inboxes | Powered by JetHome®