PM / QoS: remove duplicate call to pm_qos_update_target
authorMichael Scott <michael.scott@linaro.org>
Tue, 10 Mar 2015 20:15:02 +0000 (13:15 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 18 Mar 2015 12:22:28 +0000 (13:22 +0100)
commit8dbaea2b3d24e3a77e6a853ff76c19c5a6052f4e
tree6022017739773d9802ecd8c7288743b38ca985c3
parent84ba11a6ee549b2727a3b83d3c1b455df1c7ebcd
PM / QoS: remove duplicate call to pm_qos_update_target

In 3.10.y backport patch 1dba303727f52ea062580b0a9b3f0c3b462769cf,
the logic to call pm_qos_update_target was moved to __pm_qos_update_request.
However, the original code was left in function pm_qos_update_request.

Currently, if pm_qos_update_request is called where new_value !=
req->node.prio then pm_qos_update_target will be called twice in a row.
Once in pm_qos_update_request and then again in the following call to
_pm_qos_update_request.

Removing the left over code from pm_qos_update_request stops this second
call to pm_qos_update_target where the work of removing / re-adding the
new_value in the constraints list would be duplicated.

Signed-off-by: Michael Scott <michael.scott@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
kernel/power/qos.c