From: Vinod Koul <vkoul@kernel.org>
To: linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev,
Marco Crivellari <marco.crivellari@suse.com>
Cc: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Chen-Yu Tsai <wens@kernel.org>
Subject: Re: [PATCH] phy: sun4i-usb: replace use of system_wq with system_percpu_wq
Date: Wed, 14 Jan 2026 19:31:29 +0530 [thread overview]
Message-ID: <176839928954.937923.15095865192573263958.b4-ty@kernel.org> (raw)
In-Reply-To: <20251105152023.259813-1-marco.crivellari@suse.com>
On Wed, 05 Nov 2025 16:20:23 +0100, Marco Crivellari wrote:
> Currently if a user enqueues a work item using schedule_delayed_work() the
> used wq is "system_wq" (per-cpu wq) while queue_delayed_work() use
> WORK_CPU_UNBOUND (used when a cpu is not specified). The same applies to
> schedule_work() that is using system_wq and queue_work(), that makes use
> again of WORK_CPU_UNBOUND.
>
> This lack of consistency cannot be addressed without refactoring the API.
>
> [...]
Applied, thanks!
[1/1] phy: sun4i-usb: replace use of system_wq with system_percpu_wq
commit: 877686f9f42b58b04e4e25d07034bc95cadc20f3
Best regards,
--
~Vinod
next prev parent reply other threads:[~2026-01-14 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 15:20 [PATCH] phy: sun4i-usb: replace use of system_wq with system_percpu_wq Marco Crivellari
2025-11-05 16:44 ` Jernej Škrabec
2026-01-13 9:07 ` Marco Crivellari
2026-01-14 14:01 ` Vinod Koul [this message]
2026-01-14 14:15 ` 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=176839928954.937923.15095865192573263958.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=samuel@sholland.org \
--cc=tj@kernel.org \
--cc=wens@kernel.org \
/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