GitHub PushEvent at 2014-09-01 22:10:56
Repository: Alucard-Kernel-jfltexx
Actor: Alucard24
Payload: {"shas":[["56f86d699ebd53d24abc00f86a3c76a75506bb00","ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","workqueue: change BUG_ON() to WARN_ON()\n\nThis BUG_ON() can be triggered if you call schedule_work() before\ncalling INIT_WORK().  It is a bug definitely, but it's nicer to just\nprint a stack trace and return.\n\nReported-by: Matt Renzelmann <mjr@cs.wisc.edu>\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Tejun Heo <tj@kernel.org>","Dan Carpenter",true],["3fd4e45f967bbcfe98159c92a097e902098fcd6f","6cb58b8f5386ab909543bfc6eef5a0bd2950ca0a@gmail.com","mako_thermal: use WQ_RESCUER till it will be replace fully by WQ_MEM_RECLAIM.","alucard24",true],["53f5f274956591537eb96416d628ca1021ea04f6","6cb58b8f5386ab909543bfc6eef5a0bd2950ca0a@gmail.com","Disabled CONFIG_MAKO_THERMAL_STATS","alucard24",true],["036bb414d80a3d8bf661740f780bfed005de090c","6cb58b8f5386ab909543bfc6eef5a0bd2950ca0a@gmail.com","Use intelli_thermal. I need to tweak mako_thermal in a better way.","alucard24",true],["691e4b90b85d378f26910bf9a1baba3b85e3b4b5","6cb58b8f5386ab909543bfc6eef5a0bd2950ca0a@gmail.com","Implemented CPU_VOLTAGE_CONTROL.","alucard24",true],["3ff591b46a47399c3efa2ede8fd466f15b54bb65","6cb58b8f5386ab909543bfc6eef5a0bd2950ca0a@gmail.com","GPU_VOLTAGE_CONTROL: cosmetic work","alucard24",true],["f035543c5589c305647f1901027eb4619081b09e","6cb58b8f5386ab909543bfc6eef5a0bd2950ca0a@gmail.com","Restored default intelli_thermal parameter settings.","Alucard24",true],["c9d1e86a5490d829afbfb877c6265cff32c947f5","6cb58b8f5386ab909543bfc6eef5a0bd2950ca0a@gmail.com","New Official kernel.","alucard24",true],["9d6dd6634a79425df0623a78598c412ae157096b","5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","cpufreq / core: Fix typo in comment describing show_bios_limit()\n\nshow_bios_limit is mistakenly written as show_scaling_driver in a comment\ndescribing purpose of show_bios_limit() routine.\n\nFix it.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","viresh kumar",true],["46b5f8abb288596287a71e2484746620290ea6e3","5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","cpufreq: Improve debug prints\n\nWith debug options on, it is difficult to locate cpufreq core's debug prints.\nFix this by prefixing debug prints with KBUILD_MODNAME.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","Viresh Kumar",true],["0d9f3fcff627a0046bce6bdf025fbeb29252435e","5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","cpufreq: return early from __cpufreq_driver_getavg()\n\nThere is no need to do cpufreq_get_cpu() and cpufreq_put_cpu() for drivers that\ndon't support getavg() routine.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","Viresh Kumar",true],["708a084a922f89e321910a7d3e1c13485e4d7491","5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","cpufreq: Fix sparse warning by making local function static\n\ncpufreq_disabled() is a local function, so should be marked static.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","Viresh Kumar",true],["5e67edfe847bea597298612f4472b2211cbf6a0d","5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","cpufreq: Avoid calling cpufreq driver's target() routine if target_freq == policy->cur\n\nAvoid calling cpufreq driver's target() routine if new frequency is same as\npolicies current frequency.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","Viresh Kumar",true],["534f55bc6e6f3c9334d416cc6c0c850d318b372f","5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","cpufreq: Make sure target freq is within limits\n\n__cpufreq_driver_target() must not pass target frequency beyond the\nlimits of current policy.\n\nToday most of cpufreq platform drivers are doing this check in their\ntarget routines. Why not move it to __cpufreq_driver_target()?\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","Viresh Kumar",true],["c4e1b87081b269813b4c79396d9dc83d2c7733ad","fc379137a64feb86ce38ec5811a14280acc1ccfc@samsung.com","cpufreq: Remove unnecessary initialization of a local variable\n\nRemove an unnecessary initializer for the 'ret' variable in\n__cpufreq_set_policy().\n\n[rjw: Modified the subject and changelog slightly.]\nSigned-off-by: Jingoo Han <jg1.han@samsung.com>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","Jingoo Han",true],["ff66f5a4ee4b6113ed0efb3e06c7197b9725a03f","ae947f3c8df96e1dc851c5e3e5a930ce6d3f1f74@windriver.com","PM / tracing: remove deprecated power trace API\n\nThe text in Documentation said it would be removed in 2.6.41;\nthe text in the Kconfig said removal in the 3.1 release.  Either\nway you look at it, we are well past both, so push it off a cliff.\n\nNote that the POWER_CSTATE and the POWER_PSTATE are part of the\nlegacy tracing API.  Remove all tracepoints which use these flags.\nAs can be seen from context, most already have a trace entry via\ntrace_cpu_idle anyways.\n\nAlso, the cpufreq/cpufreq.c PSTATE one is actually unpaired, as\ncompared to the CSTATE ones which all have a clear start/stop.\nAs part of this, the trace_power_frequency also becomes orphaned,\nso it too is deleted.\n\nSigned-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>\nAcked-by: Steven Rostedt <rostedt@goodmis.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\n\nConflicts:\n\tarch/x86/kernel/process.c","Paul Gortmaker",true]],"size":16,"ref":"refs/heads/my-aospv2-4.4","head":"ff66f5a4ee4b6113ed0efb3e06c7197b9725a03f"}