linux-next broken for MIPS by b87077280b7271c5310237e127b0fe423d443e0f(mips: merge the identical "return from syscall" per-ABI code)

All of lore.kernel.org
 help / color / mirror / Atom feed

From: David Daney <ddaney.cavm@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Ralf Baechle <ralf@linux-mips.org>
Subject: linux-next broken for MIPS by b87077280b7271c5310237e127b0fe423d443e0f(mips: merge the identical "return from syscall" per-ABI code)
Date: Tue, 05 Jun 2012 12:42:39 -0700	[thread overview]
Message-ID: <4FCE612F.6020000@gmail.com> (raw)

As shown here:

http://kisskb.ellerman.id.au/kisskb/buildresult/6442834/

Commit b87077280b7271c5310237e127b0fe423d443e0f(mips: merge the 
identical "return from syscall" per-ABI code) breaks MIPS.

I suggest that on arch/mips/kernel/entry.S:173 that you do:

s/bz/beqz/

I suspect that will fix the assembler error.  Other than that, I make no 
claims about the correctness of the code in general.

David Daney

                 reply	other threads:[~2012-06-05 19:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4FCE612F.6020000@gmail.com \
    --to=ddaney.cavm@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=ralf@linux-mips.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.