[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAofZF4+nDAWQrKEPTwR9vtfECevdjm=nsXR+5wUwGQCzsv=SA@mail.gmail.com>
Date: Wed, 14 Jan 2026 10:20:29 +0100
From: Marco Crivellari <marco.crivellari@...e.com>
To: Ping-Ke Shih <pkshih@...ltek.com>
Cc: Johannes Berg <johannes@...solutions.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>, Tejun Heo <tj@...nel.org>,
Lai Jiangshan <jiangshanlai@...il.com>, Frederic Weisbecker <frederic@...nel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>, Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH 0/3] replace system_unbound_wq, add WQ_PERCPU to alloc_workqueue
On Wed, Jan 14, 2026 at 1:42 AM Ping-Ke Shih <pkshih@...ltek.com> wrote:
> [...]
> The rtw88 one [1] is still queued on my hand, because it was wrongly applied [2]
> causing regression and reverted by [3]. However, I have not rebased rtw-next
> tree on top of wireless tree, so I can't apply [1]. Do you think this is urgent?
> If so, I'd send a pull request to wireless-next right now since it is 6.19-rc5.
> I don't want frequent pull-request that maintainers have extra load.
>
> [1] https://patchwork.kernel.org/project/linux-wireless/patch/20251113160605.381777-3-marco.crivellari@suse.com/
> [2] 9c194fe4625d ("wifi: rtw88: add WQ_UNBOUND to alloc_workqueue users")
> [3] 0ff5e81e1518 ("Revert "wifi: rtw88: add WQ_UNBOUND to alloc_workqueue users"")
Hi,
I still have some other patches around, so if you have to posticipate
this to the next release is fine with me, no need to rush.
Thanks!
--
Marco Crivellari
L3 Support Engineer
Powered by blists - more mailing lists