From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tal Shorer <tal.shorer@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: linux-next: build failure after merge of the workqueues tree
Date: Fri, 3 Nov 2017 06:59:11 -0700 [thread overview]
Message-ID: <20171103135911.GS3252168@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20171102143440.67acc666@canb.auug.org.au>
On Thu, Nov 02, 2017 at 02:34:40PM +1100, Stephen Rothwell wrote:
> Hi Tejun,
>
> After merging the workqueues tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> kernel/workqueue.c: In function 'workqueue_init_early':
> kernel/workqueue.c:5561:56: error: 'cpu_isolated_map' undeclared (first use in this function)
> cpumask_andnot(wq_unbound_cpumask, cpu_possible_mask, cpu_isolated_map);
> ^
>
> Caused by commit
>
> b5149873a0c2 ("workqueue: respect isolated cpus when queueing an unbound work")
>
> interacting with commit
>
> edb9382175c3 ("sched/isolation: Move isolcpus= handling to the housekeeping code")
>
> from the tip tree.
>
> I am not sure how to fix this, so I have reverted b5149873a0c2 for today.
I'm reverting it from my tree. Tal, can you please spin up a new
patch against the sched branch? Let's either route it through sched
branch or try again after the rc1.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-11-03 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 3:34 linux-next: build failure after merge of the workqueues tree Stephen Rothwell
2017-11-03 13:59 ` Tejun Heo [this message]
2017-11-03 15:27 ` [PATCH v3 1/2] main: kernel_start: move housekeeping_init() before workqueue_init_early() Tal Shorer
2017-11-03 15:27 ` [PATCH v3 2/2] workqueue: respect isolated cpus when queueing an unbound work Tal Shorer
2017-11-06 15:26 ` Tejun Heo
2017-11-27 16:57 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2015-06-20 10:26 linux-next: build failure after merge of the workqueues tree Stephen Rothwell
2011-02-18 3:57 Stephen Rothwell
2011-02-18 9:07 ` Tejun Heo
2011-02-21 2:27 ` Stephen Rothwell
2011-02-21 5:48 ` Dmitry Torokhov
2011-02-17 3:33 Stephen Rothwell
2011-02-17 9:23 ` Tejun Heo
2011-02-09 4:12 Stephen Rothwell
2011-02-09 8:37 ` Tejun Heo
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=20171103135911.GS3252168@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=frederic@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tal.shorer@gmail.com \
--cc=tglx@linutronix.de \
/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).