From: Cunlong Li <shenxiaogll@gmail.com>
To: "Guanyou.Chen" <chenguanyou9338@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Thomas Gleixner <tglx@kernel.org>,
chenguanyou@xiaomi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] sched/fork: fix timer_slack_ns for children of RT tasks
Date: Wed, 3 Jun 2026 11:20:40 +0800 [thread overview]
Message-ID: <ah+dhve2dFMy1dRH@debian> (raw)
In-Reply-To: <20260529132902.2699687-1-chenguanyou@xiaomi.com>
On Fri, May 29, 2026 at 09:29:02PM +0800, Guanyou.Chen wrote:
> Hi Peter,
>
> Gentle ping on v3 of this series. It addresses concerns from Cunlong
> and Prateek by only changing inheritance for RT/DL parents, preserving
> documented non-RT behavior.
>
> Thanks
> Guanyou
Thanks for addressing my concern.
Reviewed-by: Cunlong Li <shenxiaogll@gmail.com>
prev parent reply other threads:[~2026-06-03 3:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 2:52 [PATCH] sched: restore timer_slack_ns when resetting RT policy on fork Guanyou.Chen
2026-05-21 3:18 ` Cunlong Li
2026-05-21 6:23 ` Guanyou Chen
2026-05-21 6:31 ` Guanyou Chen
2026-05-21 7:04 ` Peter Zijlstra
2026-05-21 7:35 ` [PATCH v2 0/2] sched: fix timer_slack_ns for children of RT tasks Guanyou.Chen
2026-05-21 7:35 ` [PATCH 1/2] sched: restore timer_slack_ns when resetting RT policy on fork Guanyou.Chen
2026-05-21 7:35 ` [PATCH 2/2] fork: fix default_timer_slack_ns inheritance from RT parent Guanyou.Chen
2026-05-22 13:09 ` [PATCH v3 0/2] sched/fork: fix timer_slack_ns for children of RT tasks Guanyou.Chen
2026-05-22 13:09 ` [PATCH v3 1/2] sched: restore timer_slack_ns when resetting RT policy on fork Guanyou.Chen
2026-06-04 18:45 ` [tip: sched/core] " tip-bot2 for Guanyou.Chen
2026-05-22 13:10 ` [PATCH v3 2/2] fork: fix default_timer_slack_ns inheritance from RT parent Guanyou.Chen
2026-05-29 13:29 ` [PATCH v3 0/2] sched/fork: fix timer_slack_ns for children of RT tasks Guanyou.Chen
2026-06-03 3:20 ` Cunlong Li [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=ah+dhve2dFMy1dRH@debian \
--to=shenxiaogll@gmail.com \
--cc=chenguanyou9338@gmail.com \
--cc=chenguanyou@xiaomi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.