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:22:34 -1000 [thread overview]
Message-ID: <aKZYutvp4BtcqFJT@slm.duckdns.org> (raw)
In-Reply-To: <CAAofZF5KtD3zdrNcGekt4=sZCAAG6_a3Pz99NzfhX3iMkqLdyw@mail.gmail.com>
Hello,
On Tue, Aug 19, 2025 at 10:41:01AM +0200, Marco Crivellari wrote:
> I'm not sure I have clearly understood what you mean here:
>
> > e.g. Network flows through the same tree but different
> > filesystems often have their own trees.
>
> With this, you mean also distinguish between e.g. fs/ext4/ fs/etx2/
> and fs/btrfs/ etc?
> So if it is the case, in the example above, it means 3 different series.
> Prefixed like this, I imagine: "workqueue: btrfs: ....".
NVM, if Christian can apply for all filesystems, that's better.
> And I guess it would be the same for drivers, eg drivers/net/
I think net should be fine with wider scope patches, actually. It's mostly
about laying things out for respective subsys maintainers so that it's
easier for them to take actions.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-08-20 23:22 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 [this message]
2025-08-21 7:44 ` Marco Crivellari
2025-08-19 12:28 ` Marco Crivellari
2025-08-20 23:19 ` Tejun Heo
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=aKZYutvp4BtcqFJT@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®