From: Lou Langholtz <ldl@chpc.utah.edu>
To: Cort Dougan <cort@ppc.kernel.org>
Cc: linuxppc-dev@lists.linuxppc.org, gdt@linuxppc.org
Subject: Re: linux-2.2.13pre15 stability w/ head.S patch
Date: Fri, 29 Oct 1999 12:13:43 -0600 [thread overview]
Message-ID: <3819E3D7.B9D7E4F3@chpc.utah.edu> (raw)
In-Reply-To: 19991028212456.B13879@chimaera.ppc.kernel.org
Cort Dougan wrote:
> The Linus tree is in sync with by the 2.2 and 2.3 right now. Have you
> tried 2.3.24 and/or 2.3.13?
That's great news. My bandwidth is so limited that checking this fact is
impracticle. So this helps a lot to know. I haven't tried 2.3.24 or 2.3.13 or
2.2.13 out yet either. Seems like 2.2.14's due out soon and I figured I'd just
wait.
> The changes here should only affect the boot since that's the only place
> they do anything. Are you sure this change improved stability and now the
> recent changes to PPP from Paul? . . .
It was more speculation in part based on diff'ing different releases to see how
much PPC specific changes had occured. I've also seen reference by others on
the linuxppc-dev list that seemed to point to this code improving things
stability wise. Maybe I just misunderstood or something. I'm kind of too
crunched for time right now to dig this out --- sorry about that. I'll try
being more thourough later on when I get more time or maybe the problem will
have just been totally fixed.
Whatever the case, thanks for considering it.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-29 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-28 18:06 linux-2.2.13pre15 stability w/ head.S patch Lou Langholtz
1999-10-28 17:39 ` David Edelsohn
1999-10-29 10:34 ` Gabriel Paubert
1999-10-29 18:11 ` David Edelsohn
1999-10-29 3:24 ` Cort Dougan
1999-10-29 18:13 ` Lou Langholtz [this message]
1999-10-30 3:58 ` Martin Costabel
1999-10-30 15:07 ` Takashi Oe
1999-10-30 18:36 ` phandel
1999-10-31 20:31 ` Geert Uytterhoeven
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=3819E3D7.B9D7E4F3@chpc.utah.edu \
--to=ldl@chpc.utah.edu \
--cc=cort@ppc.kernel.org \
--cc=gdt@linuxppc.org \
--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).