Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@embeddedalley.com>
To: linux-mips@linux-mips.org
Subject: Re: fyi, syscall() somehow broken...
Date: Thu, 09 Dec 2004 07:25:49 -0800	[thread overview]
Message-ID: <41B86E7D.3000609@embeddedalley.com> (raw)
In-Reply-To: <1102602117.28707.49.camel@shswe.inso.tuwien.ac.at>


> jfyi, something broke w/ the following commit... most notably 'ls -l'
> doesn't work anymore... reverting to yesterdays cvs state fixes the
> issues... ;-)
> 
> Working file: arch/mips/kernel/scall32-o32.S
> head: 1.18
> revision 1.18
> date: 2004/12/08 14:32:30;  author: ths;  state: Exp;  lines: +85 -102
> Fix indirect syscalls for o32, improve syscall performance a bit,
> and general code cleanup.

Someone reported this problem on the Au1x boards. Anyone else seeing 
the problem on other MIPS32 boards?

Pete

       reply	other threads:[~2004-12-09 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1102602117.28707.49.camel@shswe.inso.tuwien.ac.at>
2004-12-09 15:25 ` Pete Popov [this message]
2004-12-09 15:44   ` fyi, syscall() somehow broken Thiemo Seufer
2004-12-10  6:25     ` Thiemo Seufer

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=41B86E7D.3000609@embeddedalley.com \
    --to=ppopov@embeddedalley.com \
    --cc=linux-mips@linux-mips.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