From: Peter Zijlstra <peterz@infradead.org>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: 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>,
Philip Auld <pauld@redhat.com>,
Gabriele Monaco <gmonaco@redhat.com>,
linux-kernel@vger.kernel.org,
Bruno Goncalves <bgoncalv@redhat.com>
Subject: Re: [PATCH] sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting
Date: Fri, 6 Feb 2026 16:39:59 +0100 [thread overview]
Message-ID: <20260206153959.GT1282955@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260206-upstream-fix-deadline-piboost-b4-v1-1-14043567b89c@redhat.com>
On Fri, Feb 06, 2026 at 02:25:52PM +0100, Juri Lelli wrote:
> diff --git a/kernel/sched/syscalls.c b/kernel/sched/syscalls.c
> index 6f10db3646e7f..369e47b4ea863 100644
> --- a/kernel/sched/syscalls.c
> +++ b/kernel/sched/syscalls.c
> @@ -7,6 +7,7 @@
> * Copyright (C) 1991-2002 Linus Torvalds
> * Copyright (C) 1998-2024 Ingo Molnar, Red Hat
> */
> +#include "linux/sched/rt.h"
> #include <linux/sched.h>
> #include <linux/cpuset.h>
> #include <linux/sched/debug.h>
Is this clangd being 'helpful' ? Or an over eager AI thing? In case of
clangd, add to .clangd:
Completion:
HeaderInsertion: Never
next prev parent reply other threads:[~2026-02-06 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 13:25 [PATCH] sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting Juri Lelli
2026-02-06 15:39 ` Peter Zijlstra [this message]
2026-02-06 15:42 ` Juri Lelli
2026-02-07 8:45 ` Peter Zijlstra
2026-02-09 9:46 ` Juri Lelli
2026-02-24 13:22 ` Juri Lelli
2026-02-24 13:45 ` Peter Zijlstra
2026-02-24 14:05 ` Juri Lelli
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=20260206153959.GT1282955@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bgoncalv@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gmonaco@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pauld@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