From: Michael Ellerman <mpe@ellerman.id.au>
To: Mark Brown <broonie@kernel.org>,
Marcin Niestroj <m.niestroj@grinn-global.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Tony Lindgren <tony@atomide.com>,
Lee Jones <lee.jones@linaro.org>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: next-20160914 build: 2 failures 3 warnings (next-20160914)
Date: Thu, 15 Sep 2016 09:49:46 +1000 [thread overview]
Message-ID: <87d1k6nisl.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20160914171137.GF27974@sirena.org.uk>
Mark Brown <broonie@kernel.org> writes:
> [ Unknown signature status ]
> On Wed, Sep 14, 2016 at 09:18:08AM +0100, Build bot for Mark Brown wrote:
>
> Today's -next fails to build both arm and arm64 allmodconfig due to:
>
>> arm64-allmodconfig
>> ERROR: "irq_set_parent" [drivers/mfd/tps65217.ko] undefined!
>>
>> arm-allmodconfig
>> ERROR: "irq_set_parent" [drivers/mfd/tps65217.ko] undefined!
>
> due to 262d5cc6ceb293 (mfd: tps65217: Add support for IRQs) since
> irq_set_parent() isn't exported.
And powerpc too.
cheers
next prev parent reply other threads:[~2016-09-14 23:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 8:18 next-20160914 build: 2 failures 3 warnings (next-20160914) Build bot for Mark Brown
2016-09-14 17:11 ` Mark Brown
2016-09-14 19:58 ` Lee Jones
2016-09-14 23:49 ` Michael Ellerman [this message]
2016-09-19 10:21 ` Mark Brown
2016-09-19 10:31 ` Arnd Bergmann
2016-09-19 10:54 ` Mark Brown
2016-09-19 11:30 ` Arnd Bergmann
2016-09-19 15:31 ` Grygorii Strashko
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=87d1k6nisl.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=broonie@kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=lee.jones@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=m.niestroj@grinn-global.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox