[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAofZF6Cw5T6uZgrdyaEYX-6SBfrVzionudsw36+uROdmiGuJw@mail.gmail.com>
Date: Tue, 30 Dec 2025 11:13:23 +0100
From: Marco Crivellari <marco.crivellari@...e.com>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-kernel@...r.kernel.org, linux-sound@...r.kernel.org,
patches@...nsource.cirrus.com, 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>,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
Maciej Strozek <mstrozek@...nsource.cirrus.com>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.dev>, Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>, Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>
Subject: Re: [PATCH] ASoC: SDCA: Replace use of system_wq with system_percpu_wq
On Sat, Dec 27, 2025 at 4:15 PM Richard Fitzgerald
<rf@...nsource.cirrus.com> wrote:
> [...]
> , workqueue users must be converted to the better named new workqueues with
> > no intended behaviour changes:
> >
> > system_wq -> system_percpu_wq
> > system_unbound_wq -> system_dfl_wq
> >
>
> This seems to contradict the statement above that "after a careful
> review .. of each individual case". This looks more like every system_wq
> is converted to system_percpu_wq.
Hi Richard,
Yes you're right. Every system_wq has been converted directly to
system_percpu_wq.
I will fix the commit log.
Thank you!
--
Marco Crivellari
L3 Support Engineer
Powered by blists - more mailing lists