mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Frederic Weisbecker <frederic@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH 0/4] Workqueue: replace system wq and change alloc_workqueue callers
Date: Wed, 20 Aug 2025 13:19:44 -1000	[thread overview]
Message-ID: <aKZYEDYHYs3W2OL0@slm.duckdns.org> (raw)
In-Reply-To: <CAAofZF5U_fND+te4Sj_+TQPgZH_DDTneN2XLyY7a0niGBjGjaA@mail.gmail.com>

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

  reply	other threads:[~2025-08-20 23:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15  9:45 Marco Crivellari
2025-08-15  9:45 ` [PATCH 1/4] Workqueue: replace use of system_wq with system_percpu_wq Marco Crivellari
2025-08-15  9:45 ` [PATCH 2/4] Workqueue: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2025-08-15  9:45 ` [PATCH 3/4] Workqueue: WQ_PERCPU added to all the remaining users Marco Crivellari
2025-08-15  9:45 ` [PATCH 4/4] [Doc] Workqueue: WQ_UNBOUND doc upgraded Marco Crivellari
2025-08-15 18:04 ` [PATCH 0/4] Workqueue: replace system wq and change alloc_workqueue callers Tejun Heo
2025-08-19  8:41   ` Marco Crivellari
2025-08-20 23:22     ` Tejun Heo
2025-08-21  7:44       ` Marco Crivellari
2025-08-19 12:28   ` Marco Crivellari
2025-08-20 23:19     ` Tejun Heo [this message]
2025-08-21  7:40       ` Marco Crivellari
2025-08-21 20:29         ` Tejun Heo
2025-08-25 10:38           ` Marco Crivellari

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=aKZYEDYHYs3W2OL0@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.crivellari@suse.com \
    --cc=mhocko@suse.com \
    --cc=tglx@linutronix.de \
    /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
all inboxes | Powered by JetHome®