Re: [PATCH] sched: Fix boolean expression in move_tasks()

Peter Williams <[email protected]> wrote:
>
> > What to do?
> 
>  Suresh's patch was wrong and this was intended as an alternative. 

OIC.

>  Unfortunately, it is also in adequate and the setting of 
>  busiest_best_prio_seen needs to be moved to just after skip_for_load is 
>  set.  I have another patch that does that (and adds to the comments). 
>  Should I send that separately or roll the two patches together?

I don't mind, really - rolled together, I guess.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH] sched: Fix boolean expression in move_tasks()
  - From: Peter Williams <[email protected]>
- Re: [PATCH] sched: Fix boolean expression in move_tasks()
  - From: Andrew Morton <[email protected]>
- Re: [PATCH] sched: Fix boolean expression in move_tasks()
  - From: Peter Williams <[email protected]>

Prev by Date: Re: [PATCH 3/3] Assert notifier_block and notifier_call are not in init section
Next by Date: Re: [PATCH 3/3] Assert notifier_block and notifier_call are not in init section
Previous by thread: Re: [PATCH] sched: Fix boolean expression in move_tasks()
Next by thread: [PATCH] enable X86_PC for HOTPLUG_CPU
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]