linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Mark Brown <broonie@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: Tree for Sep 16 (kernel/sched/core.c)
Date: Tue, 17 Sep 2019 09:52:42 +0200	[thread overview]
Message-ID: <20190917075242.GB49590@gmail.com> (raw)
In-Reply-To: <1898d3c9-1997-17ce-a022-a5e28c8dc115@infradead.org>


* Randy Dunlap <rdunlap@infradead.org> wrote:

> On 9/16/19 3:38 PM, Mark Brown wrote:
> > Hi all,
> > 
> > Changes since 20190915:
> > 
> 
> on x86_64:
> 
> when CONFIG_CGROUPS is not set:
> 
>   CC      kernel/sched/core.o
> ../kernel/sched/core.c: In function ‘uclamp_update_active_tasks’:
> ../kernel/sched/core.c:1081:23: error: storage size of ‘it’ isn’t known
>   struct css_task_iter it;
>                        ^~
>   CC      kernel/printk/printk_safe.o
> ../kernel/sched/core.c:1084:2: error: implicit declaration of function ‘css_task_iter_start’; did you mean ‘__sg_page_iter_start’? [-Werror=implicit-function-declaration]
>   css_task_iter_start(css, 0, &it);
>   ^~~~~~~~~~~~~~~~~~~
>   __sg_page_iter_start
> ../kernel/sched/core.c:1085:14: error: implicit declaration of function ‘css_task_iter_next’; did you mean ‘__sg_page_iter_next’? [-Werror=implicit-function-declaration]
>   while ((p = css_task_iter_next(&it))) {
>               ^~~~~~~~~~~~~~~~~~
>               __sg_page_iter_next
> ../kernel/sched/core.c:1091:2: error: implicit declaration of function ‘css_task_iter_end’; did you mean ‘get_task_cred’? [-Werror=implicit-function-declaration]
>   css_task_iter_end(&it);
>   ^~~~~~~~~~~~~~~~~
>   get_task_cred
> ../kernel/sched/core.c:1081:23: warning: unused variable ‘it’ [-Wunused-variable]
>   struct css_task_iter it;
>                        ^~
> 

I cannot reproduce this build failue: I took Linus's latest which has all 
the -next scheduler commits included (ad062195731b), and an x86-64 "make 
defconfig" and a disabling of CONFIG_CGROUPS still resuls in a kernel 
that builds fine.

Thanks,

	Ingo

  reply	other threads:[~2019-09-17  7:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 22:38 linux-next: Tree for Sep 16 Mark Brown
2019-09-17  5:05 ` linux-next: Tree for Sep 16 (kernel/sched/core.c) Randy Dunlap
2019-09-17  7:52   ` Ingo Molnar [this message]
2019-09-17 13:38     ` Patrick Bellasi
     [not found]       ` <871rwf2fr0.fsf@arm.com>
2019-09-17 15:07         ` Randy Dunlap
2019-09-17 15:24       ` Randy Dunlap
2019-09-18  6:05         ` Ingo Molnar
2019-09-18 10:03           ` Patrick Bellasi
2019-09-25  1:31             ` Randy Dunlap

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=20190917075242.GB49590@gmail.com \
    --to=mingo@kernel.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).