archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <>
To: Tejun Heo <>, Thomas Gleixner <>,
	Ingo Molnar <>, "H. Peter Anvin" <>,
	Peter Zijlstra <>
Cc: Linux-Next Mailing List <>,
	Linux Kernel Mailing List <>,
	Tal Shorer <>,
	Frederic Weisbecker <>
Subject: linux-next: build failure after merge of the workqueues tree
Date: Thu, 2 Nov 2017 14:34:40 +1100	[thread overview]
Message-ID: <> (raw)

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.

Stephen Rothwell

             reply	other threads:[~2017-11-02  3:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02  3:34 Stephen Rothwell [this message]
2017-11-03 13:59 ` linux-next: build failure after merge of the workqueues tree Tejun Heo
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \

* 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).