From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20160620 build: 2 failures 9 warnings (next-20160620)
Date: Mon, 20 Jun 2016 14:42:00 +0100 [thread overview]
Message-ID: <20160620134200.GU26099@sirena.org.uk> (raw)
In-Reply-To: <E1bEwGe-0004DR-4p@optimist>
On Mon, Jun 20, 2016 at 11:17:20AM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build due to:
> arm64-allmodconfig
> ../drivers/iommu/mtk_iommu.c:27:32: fatal error: linux/of_component.h: No such file or directory
which is triggered by da4d6e6d3b3ef (iommu/mediatek: Convert DT
component matching to component_match_add_release()) - there is
presumably a dependency on some other patch series that is still in
review.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160620/c9fc8ac5/attachment.sig>
next parent reply other threads:[~2016-06-20 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1bEwGe-0004DR-4p@optimist>
2016-06-20 13:42 ` Mark Brown [this message]
2016-06-20 13:52 ` next-20160620 build: 2 failures 9 warnings (next-20160620) Joerg Roedel
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=20160620134200.GU26099@sirena.org.uk \
--to=broonie@kernel.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).