From: "Markus Hästbacka" <midian@ihme.org>
To: Nick Piggin <piggin@cyberone.com.au>,
akpm@osdl.org, mfedyk@matchmail.com
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: nicksched v30
Date: Sat, 06 Mar 2004 13:39:04 +0200 [thread overview]
Message-ID: <1078573144.1850.7.camel@midux> (raw)
In-Reply-To: <4049485B.3070104@cyberone.com.au>
On Sat, 2004-03-06 at 05:41, Nick Piggin wrote:
> Unfortunately not. The scheduler in -mm is different enough
> that porting isn't straightfoward.
>
> What does mm break for you?
I don't know about the current, but one or two versions back when I
tested the last time it printed something about unknown key for the
whole dmesg and couldn't find /dev/hd{b,c}. After investigations the
hard-drives had changed place for some reason (Not swapped place, but
they were in a weird location, can't recall which).
I'll try the new one when I have time to boot this one.
Markus
next prev parent reply other threads:[~2004-03-06 11:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 6:38 nicksched v30 Nick Piggin
2004-03-05 10:48 ` Prakash K. Cheemplavam
2004-03-05 11:09 ` Nick Piggin
2004-03-05 12:16 ` Markus Hästbacka
2004-03-05 22:48 ` Mike Fedyk
2004-03-06 3:41 ` Nick Piggin
2004-03-06 11:39 ` Markus Hästbacka [this message]
2004-03-07 0:43 ` Nick Piggin
2004-03-08 10:21 ` Markus Hästbacka
2004-03-06 5:17 ` glennpj
2004-03-26 8:33 ` Prakash K. Cheemplavam
2004-03-29 22:19 ` Arvind Autar
2004-03-30 0:17 ` Nick Piggin
2004-03-30 20:12 ` Arvind Autar
[not found] ` <b9a78ea2ef3cba17ff7976aa8e5f187d@stdbev.com>
2004-03-30 14:03 ` Arvind Autar
-- strict thread matches above, loose matches on Subject: below --
2004-03-30 19:55 n.v.t n.v.t
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=1078573144.1850.7.camel@midux \
--to=midian@ihme.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox