From: Andrew Morton <akpm@osdl.org>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: kernel@kolivas.org, mingo@elte.hu, suresh.b.siddha@intel.com,
efault@gmx.de, nickpiggin@yahoo.com.au,
linux-kernel@vger.kernel.org, kenneth.w.chen@intel.com
Subject: Re: [PATCH] sched: Fix boolean expression in move_tasks()
Date: Mon, 24 Apr 2006 19:47:46 -0700 [thread overview]
Message-ID: <20060424194746.715ddd89.akpm@osdl.org> (raw)
In-Reply-To: <444D8B6F.7050601@bigpond.net.au>
Peter Williams <pwil3058@bigpond.net.au> 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.
prev parent reply other threads:[~2006-04-25 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 23:47 [PATCH] sched: Fix boolean expression in move_tasks() Peter Williams
2006-04-25 2:13 ` Andrew Morton
2006-04-25 2:37 ` Peter Williams
2006-04-25 2:47 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060424194746.715ddd89.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=kenneth.w.chen@intel.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
--cc=suresh.b.siddha@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.