From: Florian Fainelli <florian@openwrt.org>
To: Florian Fainelli <florian@openwrt.org>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org, blogic@openwrt.org
Subject: Re: [PATCH] MIPS: SMTC: fix implicit declaration of set_vi_handler
Date: Fri, 08 Feb 2013 11:53:38 +0100 [thread overview]
Message-ID: <5114D932.5050509@openwrt.org> (raw)
In-Reply-To: <1360320314-9255-1-git-send-email-florian@openwrt.org>
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
On 02/08/2013 11:45 AM, Florian Fainelli wrote:
> This patch fixes the following implicit declaration while building with
> MIPS SMTC support enabled:
>
> arch/mips/kernel/smtc.c: In function 'setup_cross_vpe_interrupts':
> arch/mips/kernel/smtc.c:1205:2: error: implicit declaration of function
> 'set_vi_handler' [-Werror=implicit-function-declaration]
> cc1: all warnings being treated as errors
And attached the config file to reproduce the build failure.
--
Florian
[-- Attachment #2: config-fail.gz --]
[-- Type: application/gzip, Size: 10280 bytes --]
prev parent reply other threads:[~2013-02-08 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 10:45 [PATCH] MIPS: SMTC: fix implicit declaration of set_vi_handler Florian Fainelli
2013-02-08 10:53 ` Florian Fainelli [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=5114D932.5050509@openwrt.org \
--to=florian@openwrt.org \
--cc=blogic@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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