[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aKZYEDYHYs3W2OL0@slm.duckdns.org>
Date: Wed, 20 Aug 2025 13:19:44 -1000
From: Tejun Heo <tj@...nel.org>
To: Marco Crivellari <marco.crivellari@...e.com>
Cc: linux-kernel@...r.kernel.org, Lai Jiangshan <jiangshanlai@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Frederic Weisbecker <frederic@...nel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH 0/4] Workqueue: replace system wq and change
alloc_workqueue callers
Hello,
On Tue, Aug 19, 2025 at 02:28:12PM +0200, Marco Crivellari wrote:
> Sorry for another email.
>
> Another question / observation: I guess maintainers can't just pull
> the changes and merge for the next release, if the workqueue changes
> (e.g. changes in queue_work() etc) are not also merged, right?
>
> I received a reply here, in the meantime, in "Workqueue: fs: replace
> use of system_wq and add WQ_PERCPU to alloc_workqueue users"
> (https://www.spinics.net/lists/kernel/msg5811817.html).
I can prepare a branch that fs can pull but aren't all the prerequisites
already in the master branch from the last cycle?
Thanks.
--
tejun
Powered by blists - more mailing lists