So, this is fixing a regression, right? If so, you need to provide a proper "Fixes: " tag identifying the commit that introduced the bug. I'm also finding it hard to believe that forcing cpu 0 as a possible cpu is required. Have you considered contacting the timer subsystem maintainers and asked them to remove this assumption? Thank you. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html