https://bugzilla.kernel.org/show_bug.cgi?id=42725
--- Comment #84 from Nate Cornell 2012-10-20 03:28:08
---
(In reply to comment #83)
> The 2.6.35 kernels do not have this problem,the trip point temp did not exist
> in those versions
Just to clarify my statement; only the trip_point_1 file
https://bugzilla.kernel.org/show_bug.cgi?id=42725
--- Comment #83 from Nate Cornell 2012-10-20 03:01:14
---
(In reply to comment #80)
> if yes, it does not seems to be a regression unless you can find out a kernel
> without this problem.
The 2.6.35 kernels do not have this problem,the trip
https://bugzilla.kernel.org/show_bug.cgi?id=48721
--- Comment #12 from j.k...@gmx.de 2012-10-19 16:08:10 ---
Hi,
I tried out several patches against stable/v3.6.2:
* Reverting 6af2d180f82151cf3d58952e35a4f96e45bc453a: result like in comment
#10.
* This [1] patch + reverting 6af2d180: upon b
https://bugzilla.kernel.org/show_bug.cgi?id=48981
--- Comment #10 from Peter 2012-10-19 15:46:25 ---
I believe that pm_runtime_{suspend,resume} is not possible for this driver
because it binds the device. Is that a correct observation from me? I went the
manual way by calling pm_runtime_{get
https://bugzilla.kernel.org/show_bug.cgi?id=45461
Ben Guthro changed:
What|Removed |Added
CC||b...@guthro.net
--
Configure bugmail: h
https://bugzilla.kernel.org/show_bug.cgi?id=48721
Jonas Jelten changed:
What|Removed |Added
CC||jel...@in.tum.de
--
Configure bugmail