[PATCH] hotplug cpu: migrate a task within its cpuset whitespace fix

[Paul Jackson]

From: Paul Jackson <pj@xxxxxxx>

Fix indentation and spacing.

Signed-off-by: Paul Jackson <pj@xxxxxxx>
Cc: Cliff Wickman <cpw@xxxxxxx>
Cc: Oleg Nesterov <oleg@xxxxxxxxxx>
Cc: Christoph Lameter <clameter@xxxxxxx>
Cc: Ingo Molnar <mingo@xxxxxxx>

---

This fix applies to and follows the other patches:
    hotplug-cpu-migrate-a-task-within-its-cpuset*.patch

 kernel/sched.c |   18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

--- 2.6.23-mm1.orig/kernel/sched.c	2007-10-16 21:59:36.035170738 -0700
+++ 2.6.23-mm1/kernel/sched.c	2007-10-16 22:05:23.624506696 -0700
@@ -5034,16 +5034,16 @@ static void move_task_off_dead_cpu(int d
 
 		/* No more Mr. Nice Guy. */
 		if (dest_cpu == NR_CPUS) {
-		cpumask_t cpus_allowed = cpuset_cpus_allowed_locked(p);
-		/*
-		 * Try to stay on the same cpuset, where the current cpuset
-		 * may be a subset of all cpus.
-		 * The cpuset_cpus_allowed_locked() variant of
-		 * cpuset_cpus_allowed() will not block
-		 * It must be called within calls to cpuset_lock/cpuset_unlock.
-		 */
+			cpumask_t cpus_allowed = cpuset_cpus_allowed_locked(p);
+			/*
+			 * Try to stay on the same cpuset, where the
+			 * current cpuset may be a subset of all cpus.
+			 * The cpuset_cpus_allowed_locked() variant of
+			 * cpuset_cpus_allowed() will not block.  It must be
+			 * called within calls to cpuset_lock/cpuset_unlock.
+			 */
 			rq = task_rq_lock(p, &flags);
-		p->cpus_allowed = cpus_allowed;
+			p->cpus_allowed = cpus_allowed;
 			dest_cpu = any_online_cpu(p->cpus_allowed);
 			task_rq_unlock(rq, &flags);
 

-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@xxxxxxx> 1.650.933.1373
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/