sched: Prevent balance_push() on remote runqueues

[linux-2.6-microblaze.git] / lib / test_kmod.c

diff --git a/lib/test_kmod.c b/lib/test_kmod.c
index 38c250f..ce15893 100644 (file)
--- a/lib/test_kmod.c
+++ b/lib/test_kmod.c
@@ -286,7 +286,7 @@ static int tally_work_test(struct kmod_test_device_info *info)
  * If this ran it means *all* tasks were created fine and we
  * are now just collecting results.
  *
- * Only propagate errors, do not override with a subsequent sucess case.
+ * Only propagate errors, do not override with a subsequent success case.
  */
 static void tally_up_work(struct kmod_test_device *test_dev)
 {
@@ -543,7 +543,7 @@ static int trigger_config_run(struct kmod_test_device *test_dev)
         * wrong with the setup of the test. If the test setup went fine
         * then userspace must just check the result of config->test_result.
         * One issue with relying on the return from a call in the kernel
-        * is if the kernel returns a possitive value using this trigger
+        * is if the kernel returns a positive value using this trigger
         * will not return the value to userspace, it would be lost.
         *
         * By not relying on capturing the return value of tests we are using
@@ -585,7 +585,7 @@ trigger_config_store(struct device *dev,
         * Note: any return > 0 will be treated as success
         * and the error value will not be available to userspace.
         * Do not rely on trying to send to userspace a test value
-        * return value as possitive return errors will be lost.
+        * return value as positive return errors will be lost.
         */
        if (WARN_ON(ret > 0))
                return -EINVAL;