From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: "Zefan Li" <lizefan.x@bytedance.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Christian Brauner" <brauner@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <shuah@kernel.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
"Juri Lelli" <juri.lelli@redhat.com>,
"Dietmar Eggemann" <dietmar.eggemann@arm.com>,
"Michal Koutný" <mkoutny@suse.com>,
"Giuseppe Scrivano" <gscrivan@redhat.com>
Subject: Re: [PATCH v8 0/7] cgroup/cpuset: Support remote partitions
Date: Mon, 18 Sep 2023 10:33:06 -1000 [thread overview]
Message-ID: <ZQi0AvvYJqaKkKG9@slm.duckdns.org> (raw)
In-Reply-To: <20230905133243.91107-1-longman@redhat.com>
Applied the series to cgroup/for-6.7.
Thanks.
--
tejun
next prev parent reply other threads:[~2023-09-18 20:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 13:32 Waiman Long
2023-09-05 13:32 ` [PATCH v8 1/7] cgroup/cpuset: Fix load balance state in update_partition_sd_lb() Waiman Long
2023-09-05 13:32 ` [PATCH v8 2/7] cgroup/cpuset: Add cpuset.cpus.exclusive.effective for v2 Waiman Long
2023-09-05 13:32 ` [PATCH v8 3/7] cgroup/cpuset: Add cpuset.cpus.exclusive " Waiman Long
2023-09-05 13:32 ` [PATCH v8 4/7] cgroup/cpuset: Introduce remote partition Waiman Long
2023-09-05 13:32 ` [PATCH v8 5/7] cgroup/cpuset: Check partition conflict with housekeeping setup Waiman Long
2023-09-05 13:32 ` [PATCH v8 6/7] cgroup/cpuset: Documentation update for partition Waiman Long
2023-09-05 13:32 ` [PATCH v8 7/7] cgroup/cpuset: Extend test_cpuset_prs.sh to test remote partition Waiman Long
2023-09-18 20:33 ` Tejun Heo [this message]
2023-10-13 15:50 ` [PATCH v8 0/7] cgroup/cpuset: Support remote partitions Michal Koutný
2023-10-13 16:03 ` Waiman Long
2023-10-24 16:13 ` Michal Koutný
2023-11-01 18:14 ` Waiman Long
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=ZQi0AvvYJqaKkKG9@slm.duckdns.org \
--to=tj@kernel.org \
--cc=brauner@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=gscrivan@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=shuah@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
all inboxes | Powered by JetHome®