[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251215115121.GA505816@ax162>
Date: Mon, 15 Dec 2025 20:51:21 +0900
From: Nathan Chancellor <nathan@...nel.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Thorsten Leemhuis <linux@...mhuis.info>,
Peter Zijlstra <peterz@...radead.org>, vincent.guittot@...aro.org,
linux-kernel@...r.kernel.org, juri.lelli@...hat.com,
dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
mgorman@...e.de, vschneid@...hat.com, tj@...nel.org,
void@...ifault.com, arighi@...dia.com, changwoo@...lia.com,
sched-ext@...ts.linux.dev,
Linux Next Mailing List <linux-next@...r.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_*())
On Mon, Dec 15, 2025 at 08:12:13AM +0100, Ingo Molnar wrote:
>
> * Thorsten Leemhuis <linux@...mhuis.info> wrote:
>
> > On 11/27/25 16:39, Peter Zijlstra wrote:
> > > Change sched_class::wakeup_preempt() to also get called for
> > > cross-class wakeups, specifically those where the woken task is of a
> > > higher class than the previous highest class.
> >
> > I suspect you might be aware of this already, but this patch afaics
> > broke compilation of today's -next for me, as reverting fixed things.
>
> Yeah, sorry about that, I fumbled a conflict resolution - should be
> fixed for tomorrow's -next.
It looks like you cleared up the rq_modified_clear() error but
rq_modified_above() is still present in kernel/sched/ext.c.
Cheers,
Nathan
Powered by blists - more mailing lists