From: "David S. Miller" <davem@redhat.com>
To: Aaron Sethman <androsyn@ratbox.org>
Cc: John <cmptradm@bigfoot.com>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.5 kernel on Sparc32
Date: Thu, 14 Jun 2001 10:00:34 -0700 (PDT) [thread overview]
Message-ID: <15144.60850.545471.763348@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0106141259580.22582-100000@squeaker.ratbox.org>
In-Reply-To: <3B142AE0.20A22175@bigfoot.com> <Pine.LNX.4.33.0106141259580.22582-100000@squeaker.ratbox.org>
Aaron Sethman writes:
> I've seen the exact same problem when trying to compile for sparc. I
> might try and fix it myself, as it doesn't seemed to be fixed in the vger
> cvs tree, or any other patch for that matter.
The problem is that we lack a maintainer for the 32-bit Sparc
port, and the situation is unlikely change until someone steps
up to take over maintaining the thing.
Later,
David S. Miller
davem@redhat.com
prev parent reply other threads:[~2001-06-14 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-14 17:01 Aaron Sethman
2001-05-29 23:04 ` John
2001-06-14 17:00 ` David S. Miller [this message]
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=15144.60850.545471.763348@pizda.ninka.net \
--to=davem@redhat.com \
--cc=androsyn@ratbox.org \
--cc=cmptradm@bigfoot.com \
--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®