PM / QoS: correct the valid range of pm_qos_class
commitd24c2a4f919d17bd1ae4f4010a38ab07ece99cf7
authorSahara <keun-o.park@windriver.com>
Thu, 20 Jun 2013 02:33:57 +0000 (20 11:33 +0900)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Thu, 20 Jun 2013 22:24:01 +0000 (21 00:24 +0200)
tree78ab757e2b4143ef5cc6a7488802634f7378fcda
parent9350de06be45a5a8b927ac6577c9d35de61c90ca
PM / QoS: correct the valid range of pm_qos_class

The valid start index for pm_qos_array is not 0, but
PM_QOS_CPU_DMA_LATENCY. There is a null_pm_qos at index 0 of
pm_qos_array.  However, null_pm_qos is not created as misc device so
that inclusion of 0 index for checking pm_qos_class especially for
file operations is not proper here.

[rjw: Changelog, a bit]
Signed-off-by: Sahara <keun-o.park@windriver.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
kernel/power/qos.c