On 22 March 2013 19:24, Borislav Petkov <bp@xxxxxxxxx> wrote: > No, you're breaking existing drivers with your changes - nobody will fix > stuff *you're* breaking. > > You need to get the hardware and test your changes on *that* hardware > too. Otherwise, the offending patches should be reverted until you can > provide a patchset which works on everything. > > Geez, the fact that I even need to explain this... You are right in every sense and i can't defend myself on that, no excuse. When i wrote those patches, i fixed many drivers and wasn't aware that acpi-cpufreq got broken. And only with the mail from Duncan i realized it. Then i tried to go thorough it & fix it and found there is some stuff in init() which is is sort of per user case dependent. And wasn't sure how exactly to fix it and so shouted for help. But yes i will give it another try to go through the driver in details and see if i can fix it. -- viresh -- 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
