cpuinit: get rid of __cpuinit, sixth regexp
This commit is the result of:

find -name "*.c" | xargs sed -i "s/^__cpuinit //g"

Change-Id: Ia723455654423f310c2762e480311d0d8dd95b31
Signed-off-by: Dennis Rassmann <showp1984@gmail.com>
cpuinit: get rid of __cpuinit, manual fixups

a few final fixups that haven't been caught by regexps

Change-Id: I1c70ea80348d495a5a4184aec9d10df0844fdd37
Signed-off-by: Dennis Rassmann <showp1984@gmail.com>
kbuild: drop cpuinit/cpuexit checks in modpost

With the removal of cpuinit/cpuexit we no longer need to
do section mismatch checks on these sections.

Drop it from modpost.

Change-Id: Ia567b9837b8d2ab2dc1db88437b644b66ff5834c
Signed-off-by: Dennis Rassmann <showp1984@gmail.com>
revert hacks for the previous misuse of __cpuinit for hotplug only functions

Change-Id: I6ece8bec1f6615f53a07628be7dffdb65eeff113
Signed-off-by: Dennis Rassmann <showp1984@gmail.com>
Fix build

Change-Id: If9aa6e334c6af8b3915ee7e4735123163bc3775a
msm_dcvs: remove no longer existing trace events

Change-Id: If3bd0f316bd626797975934fc0b7a07d0d12ce34
Signed-off-by: Dennis Rassmann <showp1984@gmail.com>
cpufreq: Fix policy getting stuck when user & kernel min/max don't overlap

Every __cpufreq_set_policy starts with checking the new policy min/max has
some overlap with the current policy min/max. This works out fine until we
end up with the policy min/max being set to a range that doesn't overlap
with the user policy min/max. Once we get into this situation, the check at
the start of __cpufreq_set_policy fails and prevents us from getting out of
this state.

This only happens when one of the CPUFREQ_ADJUST/CPUFREQ_INCOMPATIBLE
notifiers called inside __cpufreq_set_policy pick a min/max outside the
range of user policy min/max.

The real intent of the check at the start of __cpufreq_set_policy is to
make sure userspace can't set user policy min > user policy max. Since
__cpufreq_set_policy always gets called only with current user policy
min/max except when the actual user space policy min/max is changed, we can
fix the issue by simply checking the new policy min/max against current
user policy min/max.

Change-Id: Iaac805825e64d7985c41fb9052bd96baacdf3d6f
Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>
Squash bricked kernel msm_thermal (42 commits squashed)

Change-Id: I9d7e4b5d46a181a65fa963d742f853f281173e05
Signed-off-by: Dennis Rassmann <showp1984@gmail.com>
Add hook to Kconfig for touchboost

Change-Id: I33b9298ee3657ea6a2a4ff81589b46883e8aa3a2