From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Anton Blanchard <anton@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Kirill Tkhai <tkhai@yandex.ru>,
Sergei Trofimovich <slyfox@gentoo.org>
Subject: Re: New build failures in v3.13-rc1
Date: Sat, 23 Nov 2013 12:12:44 -0800 [thread overview]
Message-ID: <52910C3C.5020408@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdW-YO6WyL3F7M+q5PqATPwxD9zKLtA3tCc9-Z2wKo-mPg@mail.gmail.com>
On 11/23/2013 10:51 AM, Geert Uytterhoeven wrote:
> On Sat, Nov 23, 2013 at 7:40 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>> drivers/tty/ehv_bytechan.c:363:1: error: type defaults to 'int' in
>> declaration of 'console_initcall' [-Werror=implicit-int]
>>
>> Not really surprising as console_initcall() is not defined for modules.
>> I am a bit at loss why this is only seen now, though.
>
> On kissb that's been seens since v3.2-rc1.
>
This used to be a warning, now it is an error.
It is a side effect / result of commit 8097047217 (Makefile: enable -Werror=implicit-int
and -Werror=strict-prototypes by default). Reverting that commit fixes
this build problem, only to uncover the problem also seen with xtensa:allmodconfig:
drivers/built-in.o: In function `as3722_i2c_probe':
drivers/mfd/as3722.c:372: undefined reference to `.devm_regmap_init_i2c'
drivers/built-in.o: In function `as3722_i2c_driver_init':
drivers/mfd/as3722.c:444: undefined reference to `.i2c_register_driver'
drivers/built-in.o: In function `as3722_i2c_driver_exit':
drivers/mfd/as3722.c:444: undefined reference to `.i2c_del_driver'
Guenter
next prev parent reply other threads:[~2013-11-23 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 18:40 New build failures in v3.13-rc1 Guenter Roeck
2013-11-23 18:51 ` Geert Uytterhoeven
2013-11-23 19:13 ` Guenter Roeck
2013-11-23 20:08 ` Ard Biesheuvel
2013-11-23 20:25 ` Guenter Roeck
2013-11-23 20:12 ` Guenter Roeck [this message]
2013-11-23 21:10 ` Benjamin Herrenschmidt
2013-11-23 23:54 ` Kirill Tkhai
2013-12-30 21:03 ` Geert Uytterhoeven
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=52910C3C.5020408@roeck-us.net \
--to=linux@roeck-us.net \
--cc=anton@samba.org \
--cc=ard.biesheuvel@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slyfox@gentoo.org \
--cc=tglx@linutronix.de \
--cc=tkhai@yandex.ru \
--cc=torvalds@linux-foundation.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