public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Pingfan Liu <piliu@redhat.com>
Cc: Waiman Long <longman@redhat.com>,
	Chen Ridong <chenridong@huaweicloud.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Pierre Gondois <pierre.gondois@arm.com>,
	Ingo Molnar <mingo@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Valentin Schneider <vschneid@redhat.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	mkoutny@suse.com, linux-kernel@vger.kernel.org,
	cgroups@vger.kernel.org
Subject: Re: [PATCHv7 0/2] sched/deadline: Walk up cpuset hierarchy to decide root domain when hot-unplug
Date: Thu, 20 Nov 2025 07:00:05 -1000	[thread overview]
Message-ID: <92d3ce31b104cec08c6b9772320fc2b7@kernel.org> (raw)
In-Reply-To: <20251119095525.12019-1-piliu@redhat.com>

On Wed, Nov 19, 2025 at 05:55:23PM +0800, Pingfan Liu wrote:
> Pingfan Liu (2):
>   cgroup/cpuset: Introduce cpuset_cpus_allowed_locked()
>   sched/deadline: Walk up cpuset hierarchy to decide root domain when
>     hot-unplug

Applied 1-2 to cgroup/for-6.19.

Thanks.

--
tejun

      parent reply	other threads:[~2025-11-20 17:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19  9:55 [PATCHv7 0/2] sched/deadline: Walk up cpuset hierarchy to decide root domain when hot-unplug Pingfan Liu
2025-11-19  9:55 ` [PATCHv7 1/2] cgroup/cpuset: Introduce cpuset_cpus_allowed_locked() Pingfan Liu
2025-11-19 20:51   ` Waiman Long
2025-11-20  1:12   ` Chen Ridong
2025-11-19  9:55 ` [PATCHv7 2/2] sched/deadline: Walk up cpuset hierarchy to decide root domain when hot-unplug Pingfan Liu
2025-11-21 13:05   ` Juri Lelli
2025-11-24  1:45     ` Pingfan Liu
2025-11-24  2:24       ` Waiman Long
2025-11-24  3:56         ` Pingfan Liu
2025-11-24  4:24           ` Waiman Long
2025-11-25  3:26   ` [PATCHv2 0/2] sched/deadline: Fix potential race in dl_add_task_root_domain() Pingfan Liu
2025-11-25  3:26     ` [PATCHv2 1/2] sched/deadline: Remove unnecessary comment " Pingfan Liu
2026-01-13 10:43       ` [tip: sched/urgent] " tip-bot2 for Pingfan Liu
2025-11-25  3:26     ` [PATCHv2 2/2] sched/deadline: Fix potential race " Pingfan Liu
2026-01-13 10:43       ` [tip: sched/urgent] " tip-bot2 for Pingfan Liu
2025-11-25  8:14     ` [PATCHv2 0/2] " Juri Lelli
2026-01-07 19:57       ` Waiman Long
2026-01-08 11:42         ` Peter Zijlstra
2026-01-08 12:02           ` Pingfan Liu
2025-11-25 14:53     ` Waiman Long
2025-11-20 17:00 ` 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=92d3ce31b104cec08c6b9772320fc2b7@kernel.org \
    --to=tj@kernel.org \
    --cc=bsegall@google.com \
    --cc=cgroups@vger.kernel.org \
    --cc=chenridong@huaweicloud.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=hannes@cmpxchg.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=mkoutny@suse.com \
    --cc=peterz@infradead.org \
    --cc=pierre.gondois@arm.com \
    --cc=piliu@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@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