http://bugzilla.kernel.org/show_bug.cgi?id=12826 ------- Comment #17 from anonymous@xxxxxxxxxxxxxxxxxxxx 2009-03-06 21:39 ------- Reply-To: akpm@xxxxxxxxxxxxxxxxxxxx On Sat, 7 Mar 2009 05:18:52 +0000 Matthew Garrett <mjg@xxxxxxxxxx> wrote: > On Fri, Mar 06, 2009 at 08:46:07PM -0800, Andrew Morton wrote: > > On Sat, 7 Mar 2009 04:38:57 +0000 Matthew Garrett <mjg@xxxxxxxxxx> wrote: > > > Resulting in computers that run slower and consume more power. "My > > > script that does something stupid now gives an error" isn't a > > > regression. "My computer now overheats" is a bug that was being hidden > > > in the first place. Why don't we just fix that bug? > > > > Do the thing which I suggested, and which you deleted without comment. > > As I said, we can't print a warning without either special casing > p4-clockmod in the core That patch already special-cased p4-clockmod in the core. > or adding code to every driver that will only be > relevant for p4-clockmod. It also means another 6 months of computers > running slower and consuming more power. Special-casing p4-clockmod will not affect other drivers. > > Or something else! Just don't break existing userspace code, and > > people's computers. I'm sure you can manage this. > > I'd be thrilled to avoid fixing people's computers, but that means they > need to report the bug about their machine overheating. Breaking code > that is doing something actively harmful is a feature rather than a bug, > so I'm less concerned about that. I don't know what that means. Please find a way to fix these regressions. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- 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
