I think the summary says it all. It has been in the tree since nov-2006, no changes since 12-mar-2007 and only open bug is a feature-request (#152810) not updated since dec-2006. I am running cpufreqd-2.2.1 on one of my laptops without any problem.
Another vote for stabilizing it from me ... no problems either
*** This bug has been marked as a duplicate of bug 194798 ***
Bleh, wrong bug, sorry.
Bomp? Is there any action here or is this bug going to be open forever? For me I do not even use the package any longer as I have fallen back to use "ondemand" by default in my kernels. But this bug takes up space in my "my bugs"-list, so could someone please take a look at it? Or should I close it myself?
2.2.1 wont go stable thanks