From: Tejun Heo <tj@kernel.org>
To: Chen Ridong <chenridong@huaweicloud.com>
Cc: longman@redhat.com, hannes@cmpxchg.org, mkoutny@suse.com,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
lujialin4@huawei.com
Subject: Re: [PATCH -next v2 0/6] cpuset: further separate v1 and v2 implementations
Date: Thu, 18 Dec 2025 08:39:22 -1000 [thread overview]
Message-ID: <199daf7b81a301a7709e586ed3ffe49e@kernel.org> (raw)
In-Reply-To: <20251218093141.2687291-1-chenridong@huaweicloud.com>
> Chen Ridong (6):
> cpuset: add lockdep_assert_cpuset_lock_held helper
> cpuset: add cpuset1_online_css helper for v1-specific operations
> cpuset: add cpuset1_init helper for v1 initialization
> cpuset: move update_domain_attr_tree to cpuset_v1.c
> cpuset: separate generate_sched_domains for v1 and v2
> cpuset: remove v1-specific code from generate_sched_domains
Applied 1-6 to cgroup/for-6.20.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-12-18 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 9:31 [PATCH -next v2 0/6] cpuset: further separate v1 and v2 implementations Chen Ridong
2025-12-18 9:31 ` [PATCH -next v2 1/6] cpuset: add lockdep_assert_cpuset_lock_held helper Chen Ridong
2025-12-18 9:31 ` [PATCH -next v2 2/6] cpuset: add cpuset1_online_css helper for v1-specific operations Chen Ridong
2025-12-18 9:31 ` [PATCH -next v2 3/6] cpuset: add cpuset1_init helper for v1 initialization Chen Ridong
2025-12-18 9:31 ` [PATCH -next v2 4/6] cpuset: move update_domain_attr_tree to cpuset_v1.c Chen Ridong
2025-12-18 9:31 ` [PATCH -next v2 5/6] cpuset: separate generate_sched_domains for v1 and v2 Chen Ridong
2025-12-18 9:31 ` [PATCH -next v2 6/6] cpuset: remove v1-specific code from generate_sched_domains Chen Ridong
2025-12-18 16:30 ` [PATCH -next v2 0/6] cpuset: further separate v1 and v2 implementations Waiman Long
2025-12-18 18:39 ` Tejun Heo [this message]
2025-12-19 0:42 ` Chen Ridong
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=199daf7b81a301a7709e586ed3ffe49e@kernel.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huaweicloud.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lujialin4@huawei.com \
--cc=mkoutny@suse.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