From: Mark Brown <broonie@kernel•org>
To: Brian Masney <masneyb@onstation•org>,
Linus Walleij <linus.walleij@linaro•org>,
Andy Gross <andy.gross@linaro•org>,
David Brown <david.brown@linaro•org>,
Stephen Boyd <sboyd@kernel•org>,
Marc Zyngier <marc.zyngier@arm•com>
Cc: linaro-kernel@lists•linaro.org,
kernel-build-reports@lists•linaro.org,
linux-arm-msm@vger•kernel.org, linux-gpio@vger•kernel.org,
linux-next@vger•kernel.org, linux-arm-kernel@lists•infradead.org
Subject: Re: next-20190201 build: 2 failures 19 warnings (next-20190201)
Date: Sat, 2 Feb 2019 15:39:54 +0000 [thread overview]
Message-ID: <20190202153954.GK20797@sirena.org.uk> (raw)
In-Reply-To: <E1gpgTf-0002ZN-NF@optimist>
[-- Attachment #1.1: Type: text/plain, Size: 446 bytes --]
On Fri, Feb 01, 2019 at 09:35:59PM +0000, Build bot for Mark Brown wrote:
Friday's -next fails to build an arm64 allmodconfig due to (among other
things):
> arm64-allmodconfig
> ERROR: "irq_chip_set_wake_parent" [drivers/pinctrl/qcom/pinctrl-spmi-gpio.ko] undefined!
due to ca69e2d165eb3d060cc9 (qcom: spmi-gpio: add support for
hierarchical IRQ chip) as the driver can be built as a module but the
above symbol is not exported.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-02 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1gpgTf-0002ZN-NF@optimist>
2019-02-02 15:23 ` next-20190201 build: 2 failures 19 warnings (next-20190201) Mark Brown
2019-02-02 15:39 ` Mark Brown [this message]
2019-02-03 12:38 ` Brian Masney
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=20190202153954.GK20797@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=andy.gross@linaro$(echo .)org \
--cc=david.brown@linaro$(echo .)org \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-gpio@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marc.zyngier@arm$(echo .)com \
--cc=masneyb@onstation$(echo .)org \
--cc=sboyd@kernel$(echo .)org \
/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