From: Benjamin Herrenschmidt <bh40@calva.net>
To: Kaoru Fukui <k_fukui@highway.ne.jp>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.4.0test13 + Dual G4
Date: Wed, 27 Dec 2000 10:55:32 +0100 [thread overview]
Message-ID: <19341121032716.6201@192.168.1.2> (raw)
In-Reply-To: <20001227041316.Postino-032677@smtp01.highway.ne.jp>
>Yesterday linux_2_5`s source was broken for SMP.
>SingleCPU kernel was very well.
>
>Now I'm puting kernel-2.4.0-test13pre3ac4 from linux_2_3.
Be careful not to mismatch linux_2_3 and linuxppc_2_3. These are 2
different trees on fsmlabs.com. (linux_2_3 is linus tree while
linuxppc_2_3 is the PPC tree). It's possible that Paul's latest SMP fixes
did not yet make it into _2_5.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-27 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-22 22:22 2.4.0test13 + Dual G4 Chris Backas
2000-12-22 22:54 ` Kaoru Fukui
2000-12-26 18:29 ` Benjamin Herrenschmidt
2000-12-26 19:13 ` Kaoru Fukui
2000-12-27 9:55 ` Benjamin Herrenschmidt [this message]
2000-12-27 21:27 ` Kaoru Fukui
2000-12-27 22:02 ` Kaoru Fukui
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=19341121032716.6201@192.168.1.2 \
--to=bh40@calva.net \
--cc=k_fukui@highway.ne.jp \
--cc=linuxppc-dev@lists.linuxppc.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 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).