From: Nick Piggin <piggin@cyberone.com.au>
To: "Markus Hästbacka" <midian@ihme.org>
Cc: akpm@osdl.org, mfedyk@matchmail.com,
Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: nicksched v30
Date: Sun, 07 Mar 2004 11:43:13 +1100 [thread overview]
Message-ID: <404A7021.309@cyberone.com.au> (raw)
In-Reply-To: <1078573144.1850.7.camel@midux>
Markus Hästbacka wrote:
>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.
>
>
That would be good. Most stuff in mm is slated to get into the
official tree sooner or later, so finding problems sooner is
obviously preferable. Thanks
next prev parent reply other threads:[~2004-03-07 0:43 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
2004-03-07 0:43 ` Nick Piggin [this message]
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=404A7021.309@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--cc=midian@ihme.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 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.