From: Matthew Wilcox <willy@debian.org>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] 2.5 status update 2002-11-29
Date: Fri, 29 Nov 2002 19:03:37 +0000 [thread overview]
Message-ID: <20021129190337.W1586@parcelfarce.linux.theplanet.co.uk> (raw)
We've merged 2.5.50 into our tree. It boots on an A500 (uniprocessor)
and compiles for most common configurations. Userspace apps still crash
a lot. Our diff vs Linus' tree is 536k, which seems like a lot, except
that it was around 2.7MB in the 2.5.44 timeframe. It compresses down to
about 130k which is comparable with other architectures.
For the curious, this is how it breaks down:
parisc-hil.diff 167064
parisc-misc.diff 46402
parisc-ps2.diff 60152
parisc-scsi.diff 44026
parisc-sti.diff 162164
I'm hoping Linus will take parisc-ps2.diff & parisc-misc.diff soon.
Rusty's promised to fix the module situation.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next reply other threads:[~2002-11-29 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 19:03 Matthew Wilcox [this message]
2002-11-29 19:22 ` [parisc-linux] 2.5 status update 2002-11-29 Carlos O'Donell
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=20021129190337.W1586@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=parisc-linux@parisc-linux.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