From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bjorn Helgaas Subject: Re: linux-next: rr tree build failure Date: Mon, 3 Aug 2009 11:55:27 -0600 Message-ID: <200908031155.28386.bjorn.helgaas@hp.com> References: <20090803133203.81174a8e.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Return-path: Received: from g1t0029.austin.hp.com ([15.216.28.36]:8435 "EHLO g1t0029.austin.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753269AbZHCRzb (ORCPT ); Mon, 3 Aug 2009 13:55:31 -0400 In-Reply-To: <20090803133203.81174a8e.sfr@canb.auug.org.au> Content-Disposition: inline Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Rusty Russell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Len Brown On Sunday 02 August 2009 09:32:03 pm Stephen Rothwell wrote: > Hi Rusty, > > Today's linux-next build (x86_64 allmodconfig) failed like this: > > drivers/acpi/osl.c: In function 'bind_to_cpu0': > drivers/acpi/osl.c:194: error: implicit declaration of function 'set_cpus_allowed' > > Caused by commit 74b5820808215f65b70b05a099d6d3c969b82689 ("ACPI: bind > workqueues to CPU 0 to avoid SMI corruption") (from the acpi tree but now > in Linus' tree) interacting with commit > 17e249fb40c814a72f08c1356cb47ec9f87f81a8 > ("cpumask:remove-set_cpus_allowed") from the rr tree. > > I have reverted that rr tree commit for today. Looks like I'm doing this the wrong way (by passing a cpumask on the stack). I'll try to figure out the approved way of doing this and send a followup patch. Bjorn