All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Mark Mason <mmason@upwardaccess.com>
Cc: linux-mips@linux-mips.org
Subject: Re: linux-mips.git broken compiling for smp targets
Date: Fri, 25 Sep 2009 21:01:22 +0100	[thread overview]
Message-ID: <20090925200122.GA25773@linux-mips.org> (raw)
In-Reply-To: <20090924222719.GA18095@upwardaccess.com>

On Thu, Sep 24, 2009 at 03:27:19PM -0700, Mark Mason wrote:

> I'm getting the following compiling for my bcm1480:
> 
>   CALL    scripts/checksyscalls.sh
>   CHK     include/linux/compile.h
>   CC      arch/mips/kernel/smp.o
> arch/mips/kernel/smp.c: In function `arch_send_call_function_single_ipi':
> arch/mips/kernel/smp.c:140: error: incompatible type for argument 1 of indirect function call
> make[1]: *** [arch/mips/kernel/smp.o] Error 1
> make: *** [arch/mips/kernel] Error 2
> 
> Anyone else running into this?

Yes, the code got Rusty.  I fixed that a few hours ago.

  Ralf

      reply	other threads:[~2009-09-25 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 22:27 linux-mips.git broken compiling for smp targets Mark Mason
2009-09-25 20:01 ` 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=20090925200122.GA25773@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mmason@upwardaccess.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 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.