From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756675AbdKCN7Y (ORCPT ); Fri, 3 Nov 2017 09:59:24 -0400 Received: from mail-qk0-f180.google.com ([209.85.220.180]:51154 "EHLO mail-qk0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756453AbdKCN7V (ORCPT ); Fri, 3 Nov 2017 09:59:21 -0400 X-Google-Smtp-Source: ABhQp+QC4SMbu2wmSQ5B1Ye2F24iYr7ZiolUCWMZYxUc5U3+OK4bv/cL6+Cn5pnh7knmJx4GRgGXSA== Date: Fri, 3 Nov 2017 06:59:11 -0700 From: Tejun Heo To: Stephen Rothwell Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Linux-Next Mailing List , Linux Kernel Mailing List , Tal Shorer , Frederic Weisbecker Subject: Re: linux-next: build failure after merge of the workqueues tree Message-ID: <20171103135911.GS3252168@devbig577.frc2.facebook.com> References: <20171102143440.67acc666@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171102143440.67acc666@canb.auug.org.au> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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