From: "Iain Sandoe" <iain@sandoe.co.uk>
To: toa@pop.agri.ch
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.0-test3 tree
Date: Wed, 12 Jul 2000 02:31:59 +0100 [thread overview]
Message-ID: <200007120131.CAA24936@hyperion.valhalla.net> (raw)
Tue, Jul 11, 2000 Andreas Tobler wrote:
> Iain Sandoe wrote:
>>
>> The bk rsync 2.4.0-test3 tree is not compiling (timer.c)
>> rsynced 16:00 BST [15:00 UTC/GMT]
>
> kernel/timer.c line 580: if (p->nice > DEF_NICE) (ok)
> arch/ppc/kernel/idle.c line 51: current->nice = 0; (not sure)
>
> Runs here on a wallstreet.
Thnx.
and now on a G3/Beige :-))
[doesn't solve the problem I have - no sound - but at least I can now try
and fix that :-) ]
Iain
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-12 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 1:31 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-11 15:06 2.4.0-test3 tree Iain Sandoe
2000-07-11 15:13 ` Andreas Tobler
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=200007120131.CAA24936@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toa@pop.agri.ch \
/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;
as well as URLs for NNTP newsgroup(s).