From: "Markus Hästbacka" <midian@ihme.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Nick's scheduler v19a
Date: Sun, 07 Dec 2003 23:52:35 +0200 [thread overview]
Message-ID: <1070833955.3572.2.camel@midux> (raw)
In-Reply-To: <3FCE6073.7040503@cyberone.com.au>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
Hi again Nick, I ported the patch forward to -bk1>, the problem was
here:
<snip>
- if (sync)
<snip>
That should be:
<snip>
- if (sync && (task_cpu(p) == smp_processor_id()))
<snip>
when patchin kernel/sched.c
Is this right?
Regards,
Markus
On Thu, 2003-12-04 at 00:15, Nick Piggin wrote:
> Markus Hästbacka wrote:
>
> >Hi Nick,
> >I noticed that v19a patch wont apply to 2.6.0-test11-bk1
> >
>
> Hi Markus,
> OK, thanks for the notice, I'll bring it up to date when I get time
--
"Software is like sex, it's better when it's free."
Markus Hästbacka <midian at ihme dot org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-07 21:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-15 13:11 Nick's scheduler v19a Nick Piggin
2003-11-20 20:45 ` Markus Hästbacka
2003-11-20 23:34 ` Nick Piggin
2003-11-21 6:11 ` Markus Hästbacka
2003-11-21 6:20 ` Nick Piggin
2003-11-21 9:06 ` Markus Hästbacka
2003-11-21 9:14 ` Nick Piggin
2003-11-21 9:32 ` Markus Hästbacka
2003-11-21 9:54 ` Måns Rullgård
2003-11-21 10:21 ` Markus Hästbacka
2003-11-21 16:19 ` Timothy Miller
2003-11-21 17:00 ` Markus Hästbacka
2003-11-24 7:45 ` Peter C. Ndikuwera
2004-01-12 19:40 ` Bug found (Was: Re: Nick's scheduler v19a) Markus Hästbacka
2003-12-03 16:14 ` Nick's scheduler v19a Markus Hästbacka
2003-12-03 22:15 ` Nick Piggin
2003-12-07 21:52 ` Markus Hästbacka [this message]
2003-12-07 23:05 ` Nick Piggin
[not found] <3FF79C54.4070200@cyberone.com.au>
2004-02-02 11:21 ` Markus Hästbacka
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=1070833955.3572.2.camel@midux \
--to=midian@ihme.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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.