From: Con Kolivas <kernel@kolivas.org>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Han <xiphux@gmail.com>,
William Lee Irwin III <wli@holomorphy.com>,
Jake Moilanen <moilanen@austin.ibm.com>
Subject: Re: [PATCH] plugsched - update Kconfig-1
Date: Sun, 13 Nov 2005 12:44:47 +1100 [thread overview]
Message-ID: <200511131244.48358.kernel@kolivas.org> (raw)
In-Reply-To: <43769834.7080804@bigpond.net.au>
On Sun, 13 Nov 2005 12:34, Peter Williams wrote:
> Con Kolivas wrote:
> > Here's a respin just changing the spa menu.
>
> While agreeing that PlugSched's configuration needs overhaul I don't
> think this is it as it just makes things more confusing. I'll put
> fixing the configuration code on my list of things to do. They main
> changes I see as necessary are:
>
> 1. Make the ability to select which schedulers are built in independent
> of EMBEDDED.
> 2. Only offer builtin schedulers as choice for the default scheduler.
> 3. Only build in ingosched if PLUGSCHED is not configured.
I disagree with 3. Surely people might want to build in only one scheduler
that is not ingosched without other choices.
Cheers,
Con
next prev parent reply other threads:[~2005-11-13 1:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 0:55 [ANNOUNCE][RFC] PlugSched-6.1.3 for 2.6.13 and 2.6.14-rc4 Peter Williams
2005-10-29 2:35 ` Peter Williams
2005-11-07 22:01 ` Peter Williams
2005-11-11 3:00 ` [PATCH] Staircase v13 for plugsched 6.1.3 Con Kolivas
2005-11-13 1:36 ` Peter Williams
2005-11-11 3:05 ` [PATCH] plugsched - update Kconfig Con Kolivas
2005-11-11 3:11 ` Con Kolivas
2005-11-11 3:17 ` [PATCH] plugsched - update Kconfig-1 Con Kolivas
2005-11-13 1:34 ` Peter Williams
2005-11-13 1:44 ` Con Kolivas [this message]
2005-11-13 5:22 ` Peter Williams
2005-11-13 5:37 ` Con Kolivas
2005-11-13 9:10 ` Peter Williams
2005-11-13 9:30 ` Con Kolivas
2005-11-13 22:52 ` Peter Williams
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=200511131244.48358.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moilanen@austin.ibm.com \
--cc=pwil3058@bigpond.net.au \
--cc=wli@holomorphy.com \
--cc=xiphux@gmail.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.