Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::3:1 as permitted sender) client-ip=2620:137:e000::3:1;
From:   Kalle Valo <kvalo@kernel.org>
To:     Jeff Johnson <quic_jjohnson@quicinc.com>
Cc:     Wen Gong <quic_wgong@quicinc.com>, <ath11k@lists.infradead.org>,
        <linux-wireless@vger.kernel.org>,
        Baochen Qiang <quic_bqiang@quicinc.com>
Subject: Re: [PATCH v6 03/13] wifi: ath11k: fix a possible dead lock caused
 by ab->base_lock
References: <20230920082349.29111-1-quic_wgong@quicinc.com>
        <20230920082349.29111-4-quic_wgong@quicinc.com>
        <f9f0b511-74ce-4c3b-afdf-6352faae2ddb@quicinc.com>
Date:   Mon, 25 Sep 2023 13:35:27 +0300
In-Reply-To: <f9f0b511-74ce-4c3b-afdf-6352faae2ddb@quicinc.com> (Jeff
        Johnson's message of "Thu, 21 Sep 2023 12:54:02 -0700")
Message-ID: <871qema6c0.fsf@kernel.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

Jeff Johnson <quic_jjohnson@quicinc.com> writes:

> On 9/20/2023 1:23 AM, Wen Gong wrote:
>> From: Baochen Qiang <quic_bqiang@quicinc.com>
>> spin_lock/spin_unlock are used in ath11k_reg_chan_list_event to
>> acquire/release ab->base_lock, for now this is safe because that
>
> Kalle, can you s/, for/. For/ when you pull into pending?

Yes, will do. BTW to save time for simple edits like this I don't always
reply to you, I just do the edit the silently. In case you wonder if why
I don't reply.

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

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