From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: master build: 2 failures 4 warnings (v4.8-11811-g35ff96d)
Date: Fri, 14 Oct 2016 11:33:44 +0100 [thread overview]
Message-ID: <20161014103344.GB3304@dell> (raw)
In-Reply-To: <20161011101630.xtlcpw76nwjwcbzg@sirena.org.uk>
On Tue, 11 Oct 2016, Mark Brown wrote:
> On Tue, Oct 11, 2016 at 07:30:35AM +0100, Build bot for Mark Brown wrote:
>
> Linus' tree is currently failing to build arm and arm64 allmodconfigs
> with:
>
> > arm64-allmodconfig
> > ERROR: "irq_set_parent" [drivers/mfd/tps65217.ko] undefined!
>
> > arm-allmodconfig
> > ERROR: "irq_set_parent" [drivers/mfd/tps65217.ko] undefined!
>
> due to 6556bdacf646fc (mfd: tps65217: Add support for IRQs) since
> irq_set_parent() isn't exported. This has been present in -next
> for getting on for a month, a patch was proposed adding the relevant
> export but that isn't present in -next yet.
>
> The function is being used in order to enable lazy IRQ disabling for
> threaded interrupts:
>
> https://www.spinics.net/lists/arm-kernel/msg532864.html
>
> What's the plan for getting this fixed in Linus' tree?
Here's the conversation:
https://www.spinics.net/lists/arm-kernel/msg531850.html
I'm waiting on a firm answer from Arnd and Thomas before applying
anything.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-10-14 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1btqa6-0001tx-HV@optimist>
2016-10-11 10:16 ` master build: 2 failures 4 warnings (v4.8-11811-g35ff96d) Mark Brown
2016-10-14 10:33 ` Lee Jones [this message]
2016-10-14 20:12 ` Arnd Bergmann
2016-10-17 10:49 ` Mark Brown
2016-10-17 16:50 ` Thomas Gleixner
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=20161014103344.GB3304@dell \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).