From: "J.A. Magallon" <jamagallon@able.es>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scheduler Bug (set_cpus_allowed)
Date: Sat, 8 Jun 2002 01:20:04 +0200 [thread overview]
Message-ID: <20020607232004.GA21253@werewolf.able.es> (raw)
In-Reply-To: <20020606162028.E3193@w-mikek2.des.beaverton.ibm.com> <1023475007.1137.62.camel@sinai>
On 2002.06.07 Robert Love wrote:
>
>Anyhow, with this issue, I guess we need to fix it... I'll send a patch
>to Linus.
>
Plz, could you also post it in the list ? -aa will need also...
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.19-pre10-jam2 #1 SMP vie jun 7 17:04:23 CEST 2002 i686
next prev parent reply other threads:[~2002-06-07 23:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 23:20 Scheduler Bug (set_cpus_allowed) Mike Kravetz
2002-06-07 18:36 ` Robert Love
2002-06-07 19:12 ` Mike Kravetz
2002-06-10 20:12 ` Ingo Molnar
2002-06-10 20:57 ` Mike Kravetz
2002-06-10 22:35 ` Ingo Molnar
2002-06-10 23:15 ` Mike Kravetz
2002-06-10 23:24 ` Ingo Molnar
2002-06-10 23:28 ` Robert Love
2002-06-11 0:05 ` [patch] current scheduler bits, 2.5.21 Ingo Molnar
2002-06-11 0:27 ` Robert Love
2002-06-11 17:35 ` [patch] current scheduler bits #2, 2.5.21 Ingo Molnar
2002-06-11 18:25 ` Robert Love
2002-06-11 18:33 ` [patch] current scheduler bits #3, 2.5.21 Ingo Molnar
2002-06-13 21:26 ` [PATCH] " Robert Love
2002-06-13 22:06 ` [patch] current scheduler bits #4, 2.5.21 Ingo Molnar
2002-06-07 23:20 ` J.A. Magallon [this message]
2002-06-12 0:00 ` Scheduler Bug (set_cpus_allowed) Andrea Arcangeli
2002-06-10 18:50 ` Mike Kravetz
2002-06-10 20:02 ` Ingo Molnar
2002-06-12 11:54 ` David S. Miller
2002-06-12 16:57 ` [patch] switch_mm()'s desire to run without the rq lock Ingo Molnar
2002-06-12 21:54 ` David S. Miller
2002-06-12 22:31 ` David S. Miller
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=20020607232004.GA21253@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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.