From: Waiman Long <llong@redhat.com>
To: Sun Shaojie <sunshaojie@kylinos.cn>, llong@redhat.com
Cc: cgroups@vger.kernel.org, chenridong@huaweicloud.com,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, mkoutny@suse.com,
shuah@kernel.org, tj@kernel.org
Subject: Re: [PING][PATCH v6] cpuset: Avoid invalidating sibling partitions on cpuset.cpus conflict
Date: Tue, 23 Dec 2025 01:06:24 -0500 [thread overview]
Message-ID: <52b109f4-18b1-48ae-97ff-795328bfa5a0@redhat.com> (raw)
In-Reply-To: <20251217094530.1448665-1-sunshaojie@kylinos.cn>
On 12/17/25 4:45 AM, Sun Shaojie wrote:
> Hi, Longman,
>
> Just a friendly ping regarding the patch "[PATCH v6] cpuset: Avoid
> invalidating sibling partitions on cpuset.cpus conflict" sent on
> [Mon, 1 Dec 2025 17:38:06 +0800].
> Link: https://lore.kernel.org/cgroups/20251201093806.107157-1-sunshaojie@kylinos.cn/
>
> Could you please take a look when you have a moment? We'd appreciate any
> initial feedback or suggestions you might have.
>
> Thank you again for your time and consideration.
I am sorry that I am late in reviewing your patch. I was busy in the
last few weeks. Now I will try to review your patch later this week.
Cheers,
Longman
next prev parent reply other threads:[~2025-12-23 6:06 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 1:57 [PATCH v3 0/1] cpuset: relax the overlap check for cgroup-v2 Sun Shaojie
2025-11-17 1:57 ` [PATCH v4 1/1] " Sun Shaojie
2025-11-17 7:45 ` Chen Ridong
2025-11-17 10:00 ` Sun Shaojie
2025-11-17 11:37 ` Chen Ridong
2025-11-19 10:57 ` [PATCH v5] cpuset: Avoid invalidating sibling partitions on cpuset.cpus conflict Sun Shaojie
2025-11-19 13:20 ` Michal Koutný
2025-11-20 0:57 ` Chen Ridong
2025-11-20 13:07 ` Sun Shaojie
2025-11-20 13:25 ` Chen Ridong
2025-11-21 10:33 ` Sun Shaojie
2025-11-22 1:19 ` Chen Ridong
2025-11-24 10:21 ` Sun Shaojie
2025-11-20 13:05 ` Sun Shaojie
2025-11-26 14:13 ` Michal Koutný
2025-11-27 1:57 ` Chen Ridong
2025-12-01 9:42 ` Sun Shaojie
2025-11-20 0:51 ` Chen Ridong
2025-11-20 13:07 ` Sun Shaojie
2025-11-20 13:45 ` Chen Ridong
2025-11-21 10:32 ` Sun Shaojie
2025-11-22 1:33 ` Chen Ridong
2025-11-24 10:20 ` Sun Shaojie
2025-11-24 11:33 ` Chen Ridong
2025-11-26 12:29 ` Sun Shaojie
2025-11-24 22:30 ` Waiman Long
2025-11-26 12:31 ` Sun Shaojie
2025-11-26 14:13 ` Michal Koutný
2025-11-26 19:43 ` Waiman Long
2025-11-27 1:55 ` Chen Ridong
2025-12-01 9:44 ` Sun Shaojie
2025-12-08 14:31 ` Michal Koutný
2025-12-10 10:11 ` Sun Shaojie
2025-12-11 10:59 ` Michal Koutný
2025-12-12 10:10 ` Sun Shaojie
2025-12-13 0:52 ` Chen Ridong
2025-12-17 9:09 ` Sun Shaojie
2025-12-08 14:32 ` Michal Koutný
2025-12-13 4:58 ` Waiman Long
2025-12-01 9:38 ` [PATCH v6] " Sun Shaojie
2025-12-17 9:45 ` [PING][PATCH " Sun Shaojie
2025-12-23 6:06 ` Waiman Long [this message]
2025-12-22 15:26 ` [PATCH " Michal Koutný
2025-12-23 6:03 ` Waiman Long
2025-12-25 7:30 ` Waiman Long
2025-11-19 11:03 ` [PATCH v4 1/1] cpuset: relax the overlap check for cgroup-v2 Sun Shaojie
2025-11-18 17:52 ` Michal Koutný
2025-11-19 11:04 ` Sun Shaojie
2025-11-18 19:53 ` Waiman Long
2025-11-19 11:05 ` Sun Shaojie
2025-11-17 3:23 ` [PATCH v3 0/1] " Chen Ridong
2025-11-17 5:58 ` Sun Shaojie
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=52b109f4-18b1-48ae-97ff-795328bfa5a0@redhat.com \
--to=llong@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huaweicloud.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=shuah@kernel.org \
--cc=sunshaojie@kylinos.cn \
--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