All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Tejun Heo <tj@kernel.org>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
	 Marco Crivellari <marco.crivellari@suse.com>,
	linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH wq/for-7.4 v3 1/3] workqueue: Move the initial max_active setup into a helper
Date: Tue, 27 Oct 2026 09:18:22 -0700	[thread overview]
Message-ID: <auDOqzyG7dn3uvCY@gmail.com> (raw)
In-Reply-To: <83ad009e5a67b25fd8fc495c046d7f2d@kernel.org>

On Fri, Oct 16, 2026 at 07:21:05AM -1000, Tejun Heo wrote:
> Hello, Breno.
> 
> The following is a Claude-generated review.
> 
> On Fri, Oct 09, 2026 at 05:18:34AM -0700, Breno Leitao wrote:
> > PS: Eventually, wq_init_max_active() and wq_adjust_max_active() can share
> > some code, but, keep this as a simple code movement for now, and then we
> > can come back to it.
> 
> Maybe move this below the "---" so that it stays out of the commit log?

Ack. I will remove it for in the new version, given it brings no benefit
anymore.

  reply	other threads:[~2026-10-27 16:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 12:18 [PATCH wq/for-7.4 v3 0/3] workqueue: Keep max_active and percpu_max_active in sync Breno Leitao
2026-10-09 12:18 ` [PATCH wq/for-7.4 v3 1/3] workqueue: Move the initial max_active setup into a helper Breno Leitao
2026-10-16 17:21   ` Tejun Heo
2026-10-27 16:18     ` Breno Leitao [this message]
2026-10-09 12:18 ` [PATCH wq/for-7.4 v3 2/3] workqueue: Keep the limits of both max_active domains current Breno Leitao
2026-10-16 17:21   ` Tejun Heo
2026-10-27 17:38     ` Breno Leitao
2026-10-09 12:18 ` [PATCH wq/for-7.4 v3 3/3] workqueue: Rescale max_active domains once CPU topology is known Breno Leitao
2026-10-16 17:21   ` Tejun Heo

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=auDOqzyG7dn3uvCY@gmail.com \
    --to=leitao@debian.org \
    --cc=jiangshanlai@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.crivellari@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.