[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240911130004.GS4723@noisy.programming.kicks-ass.net>
Date: Wed, 11 Sep 2024 15:00:04 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
'@...sy.programming.kicks-ass.net
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Christian Loehle <christian.loehle@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the tip tree
On Wed, Sep 11, 2024 at 08:40:15PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (arm64 defconfig)
> failed like this:
>
> drivers/cpufreq/cppc_cpufreq.c: In function 'cppc_freq_invariance_init':
> drivers/cpufreq/cppc_cpufreq.c:227:35: error: 'NSER_PER_MSEC' undeclared (first use in this function); did you mean 'NSEC_PER_MSEC'?
> 227 | .sched_runtime = NSER_PER_MSEC,
> | ^~~~~~~~~~~~~
> | NSEC_PER_MSEC
> drivers/cpufreq/cppc_cpufreq.c:227:35: note: each undeclared identifier is reported only once for each function it appears in
> drivers/cpufreq/cppc_cpufreq.c:229:17: error: request for member 'sched_period' in something not a structure or union
> 229 | .sched_period = 10 * NSEC_PER_MSEC,
> | ^
>
> Caused by commit
>
> b3a47ff09554 ("cpufreq/cppc: Use NSEC_PER_MSEC for deadline task")
>
> I have reverted that commit for today.
Thanks, I've rebased tip/sched/core and fixed it up. Sorry for the fail.
Powered by blists - more mailing lists