From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Gabriele Monaco <gmonaco@redhat.com>,
Chen Ridong <chenridong@huaweicloud.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] cgroup/cpuset: Additional housekeeping check & cleanup
Date: Wed, 05 Nov 2025 07:07:27 -1000 [thread overview]
Message-ID: <a8248fa3f61fb85f7088312aefbf2751@kernel.org> (raw)
In-Reply-To: <20251105043848.382703-1-longman@redhat.com>
> Gabriele Monaco (1):
> cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to
> update_isolation_cpumasks()
>
> Waiman Long (4):
> cgroup/cpuset: Fail if isolated and nohz_full don't leave any
> housekeeping
> cgroup/cpuset: Move up prstate_housekeeping_conflict() helper
> cgroup/cpuset: Ensure domain isolated CPUs stay in root or isolated
> partition
> cgroup/cpuset: Globally track isolated_cpus update
Applied 1-5 to cgroup/for-6.19.
Thanks.
--
tejun
prev parent reply other threads:[~2025-11-05 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 4:38 [cgroup/for-6.19 PATCH v3 0/5] cgroup/cpuset: Additional housekeeping check & cleanup Waiman Long
2025-11-05 4:38 ` [cgroup/for-6.19 PATCH v3 1/5] cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_isolation_cpumasks() Waiman Long
2025-11-05 4:38 ` [cgroup/for-6.19 PATCH v3 2/5] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping Waiman Long
2025-11-05 7:06 ` Chen Ridong
2025-11-05 4:38 ` [cgroup/for-6.19 PATCH v3 3/5] cgroup/cpuset: Move up prstate_housekeeping_conflict() helper Waiman Long
2025-11-05 6:18 ` Chen Ridong
2025-11-05 4:38 ` [cgroup/for-6.19 PATCH v3 4/5] cgroup/cpuset: Ensure domain isolated CPUs stay in root or isolated partition Waiman Long
2025-11-05 6:29 ` Chen Ridong
2025-11-05 4:38 ` [cgroup/for-6.19 PATCH v3 5/5] cgroup/cpuset: Globally track isolated_cpus update Waiman Long
2025-11-05 17:07 ` Tejun Heo [this message]
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=a8248fa3f61fb85f7088312aefbf2751@kernel.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huaweicloud.com \
--cc=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).