From: Peter Zijlstra <peterz@infradead•org>
To: Tejun Heo <tj@kernel•org>
Cc: Thorsten Leemhuis <linux@leemhuis•info>,
Nathan Chancellor <nathan@kernel•org>,
Ingo Molnar <mingo@kernel•org>,
vincent.guittot@linaro•org, linux-kernel@vger•kernel.org,
juri.lelli@redhat•com, dietmar.eggemann@arm•com,
rostedt@goodmis•org, bsegall@google•com, mgorman@suse•de,
vschneid@redhat•com, void@manifault•com, arighi@nvidia•com,
changwoo@igalia•com, sched-ext@lists•linux.dev,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: error: implicit declaration of function ‘rq_modified_clear’ (was [PATCH 5/5] sched: Rework sched_class::wakeup_preempt() and rq_modified_*())
Date: Wed, 17 Dec 2025 10:58:01 +0100 [thread overview]
Message-ID: <20251217095801.GC3708021@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20251216214229.GR3911114@noisy.programming.kicks-ass.net>
On Tue, Dec 16, 2025 at 10:42:29PM +0100, Peter Zijlstra wrote:
> On Tue, Dec 16, 2025 at 08:40:36AM -1000, Tejun Heo wrote:
>
> > Ingo, Peter, I can pull tip and resolve this from sched_ext side too but it
> > would probably be cleaner to resolve from tip side?
>
> Yeah, I'll fix it up tomorrow morning if Ingo hasn't yet. Sorry for the
> mess.
Force pushed tip/sched/core -- this issue should now hopefully be laid
to rest. Again, sorry for the mess.
prev parent reply other threads:[~2025-12-17 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251127153943.696191429@infradead.org>
[not found] ` <20251127154725.901391274@infradead.org>
2025-12-15 6:07 ` error: implicit declaration of function ‘rq_modified_clear’ (was [PATCH 5/5] sched: Rework sched_class::wakeup_preempt() and rq_modified_*()) Thorsten Leemhuis
2025-12-15 7:12 ` Ingo Molnar
2025-12-15 11:51 ` Nathan Chancellor
2025-12-16 7:02 ` Thorsten Leemhuis
2025-12-16 18:40 ` Tejun Heo
2025-12-16 21:42 ` Peter Zijlstra
2025-12-17 9:58 ` Peter Zijlstra [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=20251217095801.GC3708021@noisy.programming.kicks-ass.net \
--to=peterz@infradead$(echo .)org \
--cc=arighi@nvidia$(echo .)com \
--cc=bsegall@google$(echo .)com \
--cc=changwoo@igalia$(echo .)com \
--cc=dietmar.eggemann@arm$(echo .)com \
--cc=juri.lelli@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@leemhuis$(echo .)info \
--cc=mgorman@suse$(echo .)de \
--cc=mingo@kernel$(echo .)org \
--cc=nathan@kernel$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=sched-ext@lists$(echo .)linux.dev \
--cc=tj@kernel$(echo .)org \
--cc=vincent.guittot@linaro$(echo .)org \
--cc=void@manifault$(echo .)com \
--cc=vschneid@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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