On Tue, 4 Aug 2009 05:52:27 am Bjorn Helgaas wrote: > 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. > > Here's a patch to fix this. Since Linus' tree still contains instances > of set_cpus_allowed(), I'm guessing this patch should be added to the rr > tree? > > Bjorn Yep, my series removes it, at least for CONFIG_CPUMASK_OFFSTACK=y. Thanks! Rusty. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html