From: Brian Masney <masneyb@onstation.org>
To: Mark Brown <broonie@kernel.org>
Cc: linaro-kernel@lists.linaro.org,
kernel-build-reports@lists.linaro.org,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
David Brown <david.brown@linaro.org>,
linux-next@vger.kernel.org, linux-gpio@vger.kernel.org,
Marc Zyngier <marc.zyngier@arm.com>,
Andy Gross <andy.gross@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: next-20190201 build: 2 failures 19 warnings (next-20190201)
Date: Sun, 3 Feb 2019 07:38:42 -0500 [thread overview]
Message-ID: <20190203123842.GA8069@basecamp> (raw)
In-Reply-To: <20190202153954.GK20797@sirena.org.uk>
Hi Mark,
On Sat, Feb 02, 2019 at 03:39:54PM +0000, Mark Brown wrote:
> 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.
Thanks for the report. I submitted two patches:
https://lore.kernel.org/lkml/20190203123131.28323-1-masneyb@onstation.org/
https://lore.kernel.org/lkml/20190203123131.28323-2-masneyb@onstation.org/
I just realized that I forgot to CC you to those patches. Sorry!
Brian
prev parent reply other threads:[~2019-02-03 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1gpgTf-0002ZN-NF@optimist>
2019-02-02 15:39 ` next-20190201 build: 2 failures 19 warnings (next-20190201) Mark Brown
2019-02-03 12:38 ` Brian Masney [this message]
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=20190203123842.GA8069@basecamp \
--to=masneyb@onstation.org \
--cc=andy.gross@linaro.org \
--cc=broonie@kernel.org \
--cc=david.brown@linaro.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=sboyd@kernel.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).