On 22 March 2013 19:33, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > On Friday, March 22, 2013 01:43:34 PM bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: >> I have never gone into coding for any non-ARM platform and am really not >> aware of acpi-cpufreq driver and its users. That's why i told everybody where >> the issue is, and they just need to fix acpi-cpufreq driver with right values >> of policy->cpus (affected_cpus) and everything else would work after that. > > Which wasn't the right thing to do. > > If your changes break something, *you* (and nobody else) are responsible for > fixing that. Yes, i already replied in another mail on what actually happened. > Asking for help is obviously fine, but even if no one can (or has the time to) > help at the moment, you are still responsible for fixing the breakage. If you > aren't familiar with the code in question, it's the time for a crash course. yes, i need to do that now. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
