From: Matthias Brugger <matthias.bgg@gmail•com>
To: Mark Brown <broonie@kernel•org>,
Sascha Hauer <s.hauer@pengutronix•de>,
Daniel Kurtz <djkurtz@chromium•org>
Cc: kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
Will Deacon <will.deacon@arm•com>
Subject: Re: next-20150729 build: 2 failures 49 warnings (next-20150729)
Date: Tue, 04 Aug 2015 21:12:54 +0200 [thread overview]
Message-ID: <17C303E7-B358-486E-9E0F-83CF58F28481@gmail.com> (raw)
In-Reply-To: <20150804173849.GD20873@sirena.org.uk>
On August 4, 2015 7:38:49 PM CEST, Mark Brown <broonie@kernel•org> wrote:
>On Wed, Jul 29, 2015 at 01:44:10PM +0100, Mark Brown wrote:
>> On Wed, Jul 29, 2015 at 12:14:36PM +0100, Build bot for Mark Brown
>wrote:
>
>> Today's linux-next fails to build an arm64 allmodconfig due to:
>
>> > arm64-allmodconfig
>> > ../include/linux/platform_device.h:245:1: error: type defaults to
>'int' in declaration of 'module_init' [-Werror=implicit-int]
>> > ../include/linux/platform_device.h:250:1: error: type defaults to
>'int' in declaration of 'module_exit' [-Werror=implicit-int]
>
>> caused by c84e358718a66f76 (soc: Mediatek: Add SCPSYS power domain
>> driver) which does not include module.h. Arguably platform_device.h
>> should do that, though it's only an issue if the macro is used so...
>
>This is still breaking the build and the fix should be trivial - is
>there any ETA for a fix getting into -next?
I send a fix to arm@kernel•org but no reply yet. (sorry I'm not in front of a computer so I can't send you the link right now).
I will send a pull request tomorrow, let's see if that helps...
Matthias
next prev parent reply other threads:[~2015-08-04 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 11:14 next-20150729 build: 2 failures 49 warnings (next-20150729) Build bot for Mark Brown
2015-07-29 12:44 ` Mark Brown
2015-08-04 17:38 ` Mark Brown
2015-08-04 19:12 ` Matthias Brugger [this message]
2015-08-05 20:27 ` Kevin Hilman
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=17C303E7-B358-486E-9E0F-83CF58F28481@gmail.com \
--to=matthias.bgg@gmail$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=djkurtz@chromium$(echo .)org \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=s.hauer@pengutronix$(echo .)de \
--cc=will.deacon@arm$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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