From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Kang Yang <quic_kangyang@quicinc.com>,
ath11k@lists.infradead.org,
Jeff Johnson <quic_jjohnson@quicinc.com>,
Aditya Kumar Singh <quic_adisi@quicinc.com>,
Vasanthakumar Thiagarajan <quic_vthiagar@quicinc.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v5 0/2] wifi: ath11k: fix data out of sync for channel list for reg update
Date: Tue, 4 Feb 2025 17:44:11 -0800 [thread overview]
Message-ID: <f82f033d-e399-44d4-8291-5e17fb42366d@oss.qualcomm.com> (raw)
In-Reply-To: <12fad7bd-86cd-4c93-8fa2-35ec7b10f5e7@quicinc.com>
On 1/21/2025 12:00 AM, Kang Yang wrote:
> On 1/17/2025 2:17 PM, Kang Yang wrote:
>> Currently there are two threads to updating/fetch data of channel
>> list, and there are no synchronization for the data, it leads data out
>> of sync for channel list when doing reg update.
>>
>> So change the call flow to make sure the fetch data running after the
>> update data finished, then data of channel list become synchronization.
>>
>> Note: This patch-set is an old patch-set in public review written by
>> Wen Gong. Just continue sending it for him.
>> Link: https://lore.kernel.org/linux-wireless/20230329091235.19500-1-quic_wgong@quicinc.com/
>>
>> v5:
>> 1. rewrite commit message in patch#1.
>> 2. update copyright in patch#1, #2.
>> v4:
>> 1. rewrite commit message in patch#1, #2.
>> 2. use list_splice_tail_init() to move list entry.
>> 3. use data_lock instead of adding a new lock.
>> v3:
>> 1. rebase on tag ath-202411251703.
>> 2. add KASAN BUG report in patch #1.
>> v2:
>> 1. rewrite commit message for patch #1 and #2.
>> 2. use a local list without the spinlock held for patch #2.
>>
>
> Hi, jeff, aditya, vasanth, any comments on this patch-set?
Now pushed to 'pending'
next prev parent reply other threads:[~2025-02-05 1:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 6:17 [PATCH v5 0/2] wifi: ath11k: fix data out of sync for channel list for reg update Kang Yang
2025-01-17 6:17 ` [PATCH v5 1/2] wifi: ath11k: update channel list in reg notifier instead reg worker Kang Yang
2025-01-21 9:03 ` Aditya Kumar Singh
2025-01-17 6:17 ` [PATCH v5 2/2] wifi: ath11k: update channel list in worker when wait flag is set Kang Yang
2025-01-21 9:03 ` Aditya Kumar Singh
2025-01-21 8:00 ` [PATCH v5 0/2] wifi: ath11k: fix data out of sync for channel list for reg update Kang Yang
2025-02-05 1:44 ` Jeff Johnson [this message]
2025-02-06 0:16 ` Jeff Johnson
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=f82f033d-e399-44d4-8291-5e17fb42366d@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_adisi@quicinc.com \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_kangyang@quicinc.com \
--cc=quic_vthiagar@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