From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: [tip:sched/core 23/23] kernel/sched/topology.c:17:2: error: 'sched_debug_verbose' undeclared; did you mean 'sched_debug_setup'?
Date: Sat, 17 Apr 2021 13:42:05 +0200 [thread overview]
Message-ID: <YHrJjbbyhcpI8IAK@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210417090628.GA9196@zn.tnic>
On Sat, Apr 17, 2021 at 11:06:28AM +0200, Borislav Petkov wrote:
> On Sat, Apr 17, 2021 at 02:47:46PM +0800, kernel test robot wrote:
> > kernel/sched/topology.c: In function 'sched_debug_setup':
> > >> kernel/sched/topology.c:17:2: error: 'sched_debug_verbose' undeclared (first use in this function); did you mean 'sched_debug_setup'?
> > 17 | sched_debug_verbose = true;
>
> I guess it needs this:
>
> ---
> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> index 55232db745ac..916bb96ff9a6 100644
> --- a/kernel/sched/sched.h
> +++ b/kernel/sched/sched.h
> @@ -2364,6 +2364,7 @@ extern struct sched_entity *__pick_last_entity(struct cfs_rq *cfs_rq);
>
> #ifdef CONFIG_SCHED_DEBUG
> extern bool sched_debug_enabled;
> +extern bool sched_debug_verbose;
>
> extern void print_cfs_stats(struct seq_file *m, int cpu);
> extern void print_rt_stats(struct seq_file *m, int cpu);
>
Right, sorry for messing that up. Pushed out that commit with this
folded. If it gives any more trouble just kill the commit, it's the
topmost commit anyway.
prev parent reply other threads:[~2021-04-17 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 6:47 kernel test robot
2021-04-17 9:06 ` Borislav Petkov
2021-04-17 11:42 ` 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=YHrJjbbyhcpI8IAK@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®