From: Tomas Szepe <szepe@pinerecords.com>
To: linux-kernel@vger.kernel.org
Cc: Joris Braakman <jorisb@nl.euro.net>, aurora-sparc-devel@linuxpower.org
Subject: Re: 2.2 kernel - Ext3 & Raid patches
Date: Thu, 23 May 2002 10:42:51 +0200 [thread overview]
Message-ID: <20020523084250.GC4370@louise.pinerecords.com> (raw)
In-Reply-To: <3CEA7866.23557.390B7FFC@localhost> <20020523011144.GA4006@matchmail.com> <20020523070244.GA4370@louise.pinerecords.com> <20020523.000303.46488296.davem@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Hi,
> From: Tomas Szepe <szepe@pinerecords.com>
> Date: Thu, 23 May 2002 09:02:44 +0200
>
> > > 2. What is the "proper" fix for the patch collision between the raid
> > > patch and the ext3 patch in /include/linux/fs.h?
> >
> > Use 2.4.
>
> Impossible on sparc32 on account of the lurking SRMMU bug.
> (See yesterday's post by Joris Braakman <jorisb@nl.euro.net>.)
>
> There have been several patches posted to deal with that
> problem, you can apply them yourself or grab Marcelo's
> current 2.4.x BK tree.
Here comes for all sparc people who can't install BK:
All sparc32/sparc64 related changes since 2.4.19-pre8 in one diff
copied and fixed up by hand from
http://linux.bkbits.net:8080/linux-2.4/ChangeSet@-3w?nav=index.html
All I can claim as to the patched kernel's functionality --
it has compiled for me on sparc32. I'm going to try to boot
it next week when I'm changing disks in my server.
T.
[-- Attachment #2: patch-2.4.19-pre8-sparcfixes-upto020523-1.gz --]
[-- Type: application/x-gunzip, Size: 6688 bytes --]
next prev parent reply other threads:[~2002-05-23 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 21:40 Jon Hedlund
2002-05-22 1:21 ` Andreas Dilger
2002-05-22 10:16 ` Stephen C. Tweedie
2002-05-23 1:11 ` Mike Fedyk
2002-05-23 7:02 ` Tomas Szepe
2002-05-23 7:03 ` David S. Miller
2002-05-23 7:21 ` Tomas Szepe
2002-05-23 8:42 ` Tomas Szepe [this message]
2002-05-23 8:49 ` Stephen C. Tweedie
2002-05-23 14:52 ` Herman Oosthuysen
2002-05-23 22:25 ` Stephen C. Tweedie
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=20020523084250.GC4370@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=aurora-sparc-devel@linuxpower.org \
--cc=jorisb@nl.euro.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®