From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Jonathan Corbet <corbet@lwn.net>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Shuah Khan <shuah@kernel.org>,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Peter Hunt <pehunt@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH v4 0/5] cgroup/cpuset: Improve CPU isolation in isolated partitions
Date: Sun, 19 Nov 2023 05:23:56 -1000 [thread overview]
Message-ID: <ZVoojBi4ZoVR2mOt@slm.duckdns.org> (raw)
In-Reply-To: <20231116033405.185166-1-longman@redhat.com>
On Wed, Nov 15, 2023 at 10:34:00PM -0500, Waiman Long wrote:
> v4:
> - Update patch 1 to move apply_wqattrs_lock() and apply_wqattrs_unlock()
> down into CONFIG_SYSFS block to avoid compilation warnings.
I already applied v3 to cgroup/for-6.8. Can you please send the fix up patch
against that branch?
Thanks.
--
tejun
next prev parent reply other threads:[~2023-11-19 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 3:34 [PATCH v4 0/5] cgroup/cpuset: Improve CPU isolation in isolated partitions Waiman Long
2023-11-16 3:34 ` [PATCH v4 1/5] workqueue: Make workqueue_set_unbound_cpumask() static Waiman Long
2023-11-16 3:34 ` [PATCH v4 2/5] workqueue: Add workqueue_unbound_exclude_cpumask() to exclude CPUs from wq_unbound_cpumask Waiman Long
2023-11-16 3:34 ` [PATCH v4 3/5] selftests/cgroup: Minor code cleanup and reorganization of test_cpuset_prs.sh Waiman Long
2023-11-16 3:34 ` [PATCH v4 4/5] cgroup/cpuset: Keep track of CPUs in isolated partitions Waiman Long
2023-11-16 3:34 ` [PATCH v4 5/5] cgroup/cpuset: Take isolated CPUs out of workqueue unbound cpumask Waiman Long
2023-11-19 15:23 ` Tejun Heo [this message]
2023-11-20 17:52 ` [PATCH v4 0/5] cgroup/cpuset: Improve CPU isolation in isolated partitions 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=ZVoojBi4ZoVR2mOt@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=frederic@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=pehunt@redhat.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