Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: MIPS Linux List <linux-mips@linux-mips.org>,
	Stuart Anderson <anderson@netsweng.com>,
	David Daney <ddaney@avtrex.com>
Subject: Re: linux kernel building for mips malta target board
Date: Wed, 18 Jan 2006 13:37:59 +0000	[thread overview]
Message-ID: <20060118133759.GT6827@deprecation.cyrius.com> (raw)
In-Reply-To: <20060118130559.GB3555@linux-mips.org>

* Ralf Baechle <ralf@linux-mips.org> [2006-01-18 13:05]:
> > With current linux-mips git I still get the problem.  As a reminder,
> > the error is:
> > 
> >   CC      fs/compat_ioctl.o
> > fs/compat_ioctl.c: In function 'fd_ioctl_trans':
> > fs/compat_ioctl.c:1831: error: read-only variable '__gu_val' used as 'asm' output
> I have not been able to find some construct that keeps gcc happy and at the
> same time doesn't result in significantly worse code.  That matters because
> get_user / put_user are used very often throughout the kernel.

Who could help with that?  Maciej?  David Daney?

(See the original discussion and the proposed patch at
http://www.spinics.net/lists/mips/msg20671.html)
-- 
Martin Michlmayr
http://www.cyrius.com/

      reply	other threads:[~2006-01-18 13:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1EXLJV-0005R4-K3@real.realitydiluted.com>
2005-11-03  0:45 ` linux kernel building for mips malta target board David Daney
2005-11-03  1:02   ` Stuart Anderson
2005-11-03  1:19     ` David Daney
2005-11-03  2:20       ` Stuart Anderson
2005-11-03 16:33         ` Ralf Baechle
2006-01-18 12:52           ` Martin Michlmayr
2006-01-18 13:05             ` Ralf Baechle
2006-01-18 13:37               ` Martin Michlmayr [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=20060118133759.GT6827@deprecation.cyrius.com \
    --to=tbm@cyrius.com \
    --cc=anderson@netsweng.com \
    --cc=ddaney@avtrex.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