From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>, Y Vo <yvo@apm.com>,
Quan Nguyen <qnguyen@apm.com>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
mbrugger@suse.com
Subject: Re: next-20160309 build: 1 failures 12 warnings (next-20160309)
Date: Thu, 10 Mar 2016 17:48:25 +0530 [thread overview]
Message-ID: <56E16611.4080502@nvidia.com> (raw)
In-Reply-To: <20160310083600.GO3898@sirena.org.uk>
On Thursday 10 March 2016 02:06 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Wed, Mar 09, 2016 at 08:45:09AM +0000, Build bot for Mark Brown wrote:
>
> Yesterday's -next fails to build on an arm64 allmodconfig due to:
>
>> arm64-allmodconfig
>> ERROR: "irq_chip_eoi_parent" [drivers/gpio/gpio-xgene-sb.ko] undefined!
>> ERROR: "irq_chip_unmask_parent" [drivers/gpio/gpio-xgene-sb.ko] undefined!
>> ERROR: "irq_chip_mask_parent" [drivers/gpio/gpio-xgene-sb.ko] undefined!
>> ERROR: "irq_domain_create_hierarchy" [drivers/gpio/gpio-xgene-sb.ko] undefined!
>> ERROR: "irq_chip_set_type_parent" [drivers/gpio/gpio-xgene-sb.ko] undefined!
>> ERROR: "irq_domain_alloc_irqs_parent" [drivers/gpio/gpio-xgene-sb.ko] undefined!
>> ERROR: "irq_domain_set_hwirq_and_chip" [drivers/gpio/gpio-xgene-sb.ko] undefined!
>> ERROR: "irq_domain_reset_irq_data" [drivers/gpio/gpio-xgene-sb.ko] undefined!
> I can't immediately see when this went wrong, if it was a recent
> addition to the driver or a change in the IRQ subsystem (these functions
> just aren't exported). The driver doesn't immediately seem to have been
> changed to support modular builds, it could be a dependency.
>
>
I saw the patches for this issue from Matthias:
https://lkml.org/lkml/2016/3/4/338
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
next prev parent reply other threads:[~2016-03-10 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 8:45 next-20160309 build: 1 failures 12 warnings (next-20160309) Build bot for Mark Brown
2016-03-10 8:36 ` Mark Brown
2016-03-10 12:18 ` Laxman Dewangan [this message]
2016-03-10 12:59 ` Quan Nguyen
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=56E16611.4080502@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=qnguyen@apm.com \
--cc=yvo@apm.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