From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: bhavesh@avaya.com (Bhavesh P. Davda)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] SCHED_FIFO and SCHED_RR scheduler fix, kernel 2.2.21
Date: Fri, 21 Jun 2002 20:56:57 +0100 (BST) [thread overview]
Message-ID: <E17LUWf-0001YA-00@the-village.bc.nu> (raw)
In-Reply-To: <3D137A16.2080303@avaya.com> from "Bhavesh P. Davda" at Jun 21, 2002 01:10:14 PM
> What's going on with the kernel community? I posted a similar fix for
> the 2.4.18 kernel, and it hasn't been picked up there either.
I've not seen that one. However the -ac tree uses a different scheduler
anyway. You should check if 2.4.19pre has the same problem and if so mail
Marcelo directly a patch
next prev parent reply other threads:[~2002-06-21 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 22:12 [PATCH] SCHED_FIFO and SCHED_RR scheduler fix, kernel 2.2.21 Bhavesh P. Davda
2002-06-21 17:29 ` Alan Cox
2002-06-21 19:10 ` Bhavesh P. Davda
2002-06-21 19:56 ` Alan Cox [this message]
2002-06-23 9:47 ` 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=E17LUWf-0001YA-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bhavesh@avaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox