From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: sporadic kernel panic during boot (MPC8xx, FEC)
Date: Fri, 12 Apr 2002 11:03:58 +0200 [thread overview]
Message-ID: <3CB6A2FE.62FFB14E@imc-berlin.de> (raw)
In-Reply-To: 20020411191258.GA2785@opus.bloom.county
> > >No. -rv2.4.18 got you 2.4.18 from kernel.org, no PPC changes at all.
> > You mean it's identical to linux-2.4.18.tar.gz from kernel.org?
> Yes.
Yes. Indeed. I just compared the two trees and got
/opt/linuxppc > dircmp -s devel_2_4_18 linux
2002-04-12 10:18 Comparison of devel_2_4_18 linux Seite
1
different ./fs/binfmt_elf.c
different ./net/ipv4/udp.c
But I am still not sure if I understand what that means. Is there a
FAQ/README/HowTo about the LinuxPPC/Bitkeeper/Versionnumbering
somewhere?
Which ChangeSet or Tag stands for a stable PPC kernel?
Which ChangeSet equals (with regard to functionality) the official
linux-2.4.18 from kernel.org?
Does the ChangesSet 1.900 (which is shortly after Tag 2.4.18) contain
all the stuff that's in the offical kernel?
Thanks,
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-12 9:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 7:07 sporadic kernel panic during boot (MPC8xx, FEC) Steven Scholz
2002-04-11 7:18 ` Christian Pellegrin
2002-04-11 7:23 ` Steven Scholz
2002-04-11 7:27 ` Christian Pellegrin
2002-04-11 15:31 ` Tom Rini
2002-04-11 15:41 ` Steven Scholz
2002-04-11 19:06 ` Wolfgang Grandegger
2002-04-11 19:12 ` Tom Rini
2002-04-12 9:03 ` Steven Scholz [this message]
2002-04-12 13:33 ` Wolfgang Denk
2002-04-12 15:08 ` Tom Rini
2002-04-12 15:13 ` Steven Scholz
2002-04-12 15:25 ` Tom Rini
2002-04-12 15:25 ` Wolfgang Denk
2002-04-12 17:13 ` Tom Rini
2002-04-11 7:27 ` Wolfgang Grandegger
2002-04-11 13:00 ` Steven Scholz
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 10:00 Kári Davíðsson
2002-04-11 13:03 ` Steven Scholz
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=3CB6A2FE.62FFB14E@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).