cpufreq: schedutil: Rectify comment in sugov_irq_work() function

[mirror_ubuntu-zesty-kernel.git] / kernel / sched / cpufreq_schedutil.c

diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
index 42a220e78f00e13b417fe3b3b6b45630a80e4769..fd465931364053e52d250da6e39b883b6615e747 100644 (file)
--- a/kernel/sched/cpufreq_schedutil.c
+++ b/kernel/sched/cpufreq_schedutil.c
@@ -315,15 +315,15 @@ static void sugov_irq_work(struct irq_work *irq_work)
        sg_policy = container_of(irq_work, struct sugov_policy, irq_work);
 
        /*
-        * For Real Time and Deadline tasks, schedutil governor shoots the
-        * frequency to maximum. And special care must be taken to ensure that
-        * this kthread doesn't result in that.
+        * For RT and deadline tasks, the schedutil governor shoots the
+        * frequency to maximum. Special care must be taken to ensure that this
+        * kthread doesn't result in the same behavior.
         *
         * This is (mostly) guaranteed by the work_in_progress flag. The flag is
-        * updated only at the end of the sugov_work() and before that schedutil
-        * rejects all other frequency scaling requests.
+        * updated only at the end of the sugov_work() function and before that
+        * the schedutil governor rejects all other frequency scaling requests.
         *
-        * Though there is a very rare case where the RT thread yields right
+        * There is a very rare case though, where the RT thread yields right
         * after the work_in_progress flag is cleared. The effects of that are
         * neglected for now.
         */