From: Ingo Molnar <mingo@elte.hu>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: [PATCH]: scheduler complex macros fixes
Date: Sat, 20 Jul 2002 16:57:00 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905787@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905791@msgid-missing>
On Fri, 19 Jul 2002, Erich Focht wrote:
> The attached patch fixes problems with the "complex" macros in the
> scheduler, as discussed about a week ago with Ingo on this mailing list.
the fix has been in my tree for some time, the latest version, against
2.5.26 is at:
http://people.redhat.com/mingo/O(1)-scheduler/sched-2.5.26-B7
it has a number of other fixes as well, plus the SCHED_BATCH feature.
Ingo
next prev parent reply other threads:[~2002-07-20 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 14:54 [Linux-ia64] Re: [PATCH]: scheduler complex macros fixes mgross
2002-07-19 15:17 ` Erich Focht
2002-07-19 17:11 ` Erich Focht
2002-07-19 17:28 ` Linus Torvalds
2002-07-20 12:32 ` Erich Focht
2002-07-20 16:57 ` Ingo Molnar [this message]
2002-07-20 17:16 ` Ingo Molnar
2002-07-20 17:43 ` Ingo Molnar
2002-07-20 19:15 ` Ingo Molnar
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=marc-linux-ia64-105590701905787@msgid-missing \
--to=mingo@elte.hu \
--cc=linux-ia64@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox