From: Joerg Roedel <jroedel@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Russell King <rmk+kernel@armlinux.org.uk>,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org
Subject: Re: next-20160620 build: 2 failures 9 warnings (next-20160620)
Date: Mon, 20 Jun 2016 15:52:41 +0200 [thread overview]
Message-ID: <20160620135241.GN29948@suse.de> (raw)
In-Reply-To: <20160620134200.GU26099@sirena.org.uk>
On Mon, Jun 20, 2016 at 02:42:00PM +0100, Mark Brown wrote:
> 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.
Yes, this came to my attention already. I will remove that patch from
the iommu tree.
Thanks,
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: jroedel@suse.de (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20160620 build: 2 failures 9 warnings (next-20160620)
Date: Mon, 20 Jun 2016 15:52:41 +0200 [thread overview]
Message-ID: <20160620135241.GN29948@suse.de> (raw)
In-Reply-To: <20160620134200.GU26099@sirena.org.uk>
On Mon, Jun 20, 2016 at 02:42:00PM +0100, Mark Brown wrote:
> 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.
Yes, this came to my attention already. I will remove that patch from
the iommu tree.
Thanks,
Joerg
next prev parent reply other threads:[~2016-06-20 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 10:17 next-20160620 build: 2 failures 9 warnings (next-20160620) Build bot for Mark Brown
2016-06-20 13:42 ` Mark Brown
2016-06-20 13:42 ` Mark Brown
2016-06-20 13:52 ` Joerg Roedel [this message]
2016-06-20 13:52 ` 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=20160620135241.GN29948@suse.de \
--to=jroedel@suse.de \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.