Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: "TWEDE,ROGER (HP-Boise,ex1)" <roger_twede@hp.com>,
	Linux/MIPS Development <linux-mips@oss.sgi.com>
Subject: Re: RedHat 7.1 cross toolchain kernel build problem
Date: Fri, 30 Nov 2001 01:08:16 +1100	[thread overview]
Message-ID: <20011130010816.E638@dea.linux-mips.net> (raw)
In-Reply-To: <20011128132117.A27181@nevyn.them.org>; from dan@debian.org on Wed, Nov 28, 2001 at 01:21:17PM -0500

On Wed, Nov 28, 2001 at 01:21:17PM -0500, Daniel Jacobowitz wrote:

> If you search the list archives, I've posted patches for this several
> times.  It's a compiler bug but can be worked around in io.h.  $5($3)
> is not a legal addressing mode.

The current kernel source has replaced the inline assembler functions in
include/asm-mips/io.h thus this is no longer necessary.

  Ralf

      reply	other threads:[~2001-11-29 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28 18:06 RedHat 7.1 cross toolchain kernel build problem TWEDE,ROGER (HP-Boise,ex1)
2001-11-28 18:21 ` Daniel Jacobowitz
2001-11-29 14:08   ` Ralf Baechle [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=20011130010816.E638@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=dan@debian.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=roger_twede@hp.com \
    /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