From: Benjamin Herrenschmidt <bh40@calva.net>
To: Stefan Jeglinski <jeglin@4pi.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: whacked out 2.2.18pre17?
Date: Fri, 3 Nov 2000 16:56:44 +0100 [thread overview]
Message-ID: <19340928092828.1670@192.168.1.2> (raw)
In-Reply-To: <p04330100b627ff09296b@[192.168.0.1]>
>I am aware that this kernel is being worked on daily (that's why I
>try to rebuild it each night), but I'm a little surprised that I am
>having so much trouble with a pre17 kernel. Anybody know what's up?
>Is this thing going through such big changes that I should let it go
>for a while instead of trying each night?
Well, first try with a more recent bootx.. that may help.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-03 15:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 5:53 whacked out 2.2.18pre17? Stefan Jeglinski
2000-11-03 15:56 ` Benjamin Herrenschmidt [this message]
2000-11-04 6:03 ` Stefan Jeglinski
2000-11-04 12:47 ` Benjamin Herrenschmidt
2000-11-04 15:55 ` Stefan Jeglinski
2000-11-05 9:36 ` Michel Lanners
2000-11-05 22:59 ` Stefan Jeglinski
2000-11-06 7:12 ` Michel Lanners
2000-11-18 3:12 ` whacked out 2.2.18pre21? Stefan Jeglinski
2000-11-18 20:03 ` Stefan Jeglinski
2000-11-18 20:09 ` aic7xxx panic in 2.2.18pre21 Hollis R Blanchard
2000-11-18 21:33 ` Stefan Jeglinski
2000-11-10 6:58 ` whacked out 2.2.18pre17? [partly solved] Stefan Jeglinski
2000-11-03 23:52 ` whacked out 2.2.18pre17? Tony Mantler
2000-11-04 1:15 ` Stefan Jeglinski
2000-11-04 2:01 ` Tony Mantler
2000-11-04 12:35 ` Simon Piette
2000-11-04 15:32 ` Tony Mantler
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=19340928092828.1670@192.168.1.2 \
--to=bh40@calva.net \
--cc=jeglin@4pi.com \
--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).