The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org,  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>,
	Maximilian Luz <luzmaximilian@gmail.com>,
	 Hans de Goede <hansg@kernel.org>
Subject: Re: [PATCH] platform/surface: acpi-notify: add WQ_PERCPU to alloc_workqueue users
Date: Wed, 19 Nov 2025 16:44:32 +0200 (EET)	[thread overview]
Message-ID: <45ac7298-6053-b125-69b3-3ef198315fe8@linux.intel.com> (raw)
In-Reply-To: <CAAofZF7AbQ12-3DzpN9Ai49VzOHa3VqyfZnXSpfVq7qijO1GRQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]

On Wed, 19 Nov 2025, Marco Crivellari wrote:

> Hi,
> On Wed, Nov 19, 2025 at 12:12 PM Ilpo Järvinen
> <ilpo.jarvinen@linux.intel.com> wrote:
> >[...]
> >
> > For those system_wq changes you can follow a similar structure but alter
> > it to match what is changed in the other interface.
> >
> > This seems already okay:
> >
> > "Replace system_wq with system_percpu_wq, keeping the same behavior."
> 
> Sorry it's just to check with you before sending a useless series.
> Sounds good this, for the 2 system_percpu_wq commit logs?
> I don't think there is more to add here, because it is a wq rename.
> 
> 
> This patch continues the effort to refactor worqueue APIs, which has begun

Please fix that typo.

> with the change introducing new workqueues and a new alloc_workqueue flag:
> 
> commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
> commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag")

You should still have here the paragraph which explains the default change 
briefly, similar to what was with the WQ_PERCPU description. I suggest you 
just edit the wording in the paragraph taken from WQ_PERCPU changelog we 
agreed on at the places where functions and arguments are different.

> For more details see the Link tag below. Replace system_wq with
> system_percpu_wq, keeping the same behavior.
> 
> 
> Thanks!
> 
> 

-- 
 i.

  reply	other threads:[~2025-11-19 14:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 14:38 [PATCH] platform/surface: acpi-notify: add WQ_PERCPU to alloc_workqueue users Marco Crivellari
2025-11-18 11:29 ` Ilpo Järvinen
2025-11-18 13:27   ` Marco Crivellari
2025-11-18 14:43     ` Ilpo Järvinen
2025-11-19 10:26       ` Marco Crivellari
2025-11-19 10:38         ` Ilpo Järvinen
2025-11-19 10:56           ` Marco Crivellari
2025-11-19 11:12             ` Ilpo Järvinen
2025-11-19 11:19               ` Marco Crivellari
2025-11-19 13:48               ` Marco Crivellari
2025-11-19 14:44                 ` Ilpo Järvinen [this message]
2025-11-19 15:46                   ` Frederic Weisbecker

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=45ac7298-6053-b125-69b3-3ef198315fe8@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=hansg@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luzmaximilian@gmail.com \
    --cc=marco.crivellari@suse.com \
    --cc=mhocko@suse.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=tj@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