Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Kalle Valo <kvalo@kernel.org>
To:     Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc:     Johannes Berg <johannes@sipsolutions.net>,
        linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org,
        "David S. Miller" <davem@davemloft.net>,
        Eric Dumazet <edumazet@google.com>,
        Jakub Kicinski <kuba@kernel.org>,
        Paolo Abeni <pabeni@redhat.com>,
        Leon Romanovsky <leonro@nvidia.com>
Subject: Re: [PATCH v5 1/1] wifi: mac80211: fortify the spinlock against deadlock by interrupt
References: <20230517213101.25617-1-mirsad.todorovac@alu.unizg.hr>
        <056e71bd6a06779bfcb1ef4518a2f67f67730fe7.camel@sipsolutions.net>
        <d574c978-c2b8-f2e0-abc5-19899b4fefe6@alu.unizg.hr>
Date:   Tue, 30 May 2023 13:32:21 +0300
In-Reply-To: <d574c978-c2b8-f2e0-abc5-19899b4fefe6@alu.unizg.hr> (Mirsad Goran
        Todorovac's message of "Thu, 18 May 2023 20:50:16 +0200")
Message-ID: <87r0qyjeiy.fsf@kernel.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr> writes:

> On 5/17/23 23:34, Johannes Berg wrote:
>>>
>>> Fixes: 4444bc2116ae ("wifi: mac80211: Proper mark iTXQs for resumption")
>>> Link: https://lore.kernel.org/all/1f58a0d1-d2b9-d851-73c3-93fcc607501c@alu.unizg.hr/
>>> Reported-by: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
>>> Link: https://lore.kernel.org/all/cdc80531-f25f-6f9d-b15f-25e16130b53a@alu.unizg.hr/
>>> Signed-off-by: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
>>> Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
>>> ---
>>>
>>
>> You really should say what you changed, but anyway, it's too late - I
>> applied a previous version yesterday.
>
> Yes. Sorry, I was following Andy's advice to resend, at the wrong
> assumption that the system ate the patch after three weeks of
> inactivity. :-/

Yeah, unfortunately we maintainers are busy so sometimes it takes before
we can process patches. But you can check the patch status from
patchwork, link below. Also the wiki has more information how we use it.

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

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