From: Robin Murphy <robin.murphy@arm•com>
To: broonie@kernel•org, Marc Zyngier <maz@kernel•org>,
Joerg Roedel <jroedel@suse•de>, Frank Li <Frank.Li@nxp•com>,
Will Deacon <will@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
linux-arm-kernel@lists•infradead.org, iommu@lists•linux.dev
Subject: Re: linux-next: build failure after merge of the irqchip tree
Date: Thu, 29 Sep 2022 15:40:56 +0100 [thread overview]
Message-ID: <7f9d35bf-282f-68cf-b857-3d7e66dbaf63@arm.com> (raw)
In-Reply-To: <20220929143149.126145-1-broonie@kernel.org>
On 2022-09-29 15:31, broonie@kernel•org wrote:
> Hi all,
>
> After merging the irqchip tree, today's linux-next build (arm64
> defconfig) failed like this:
>
> /tmp/next/build/drivers/irqchip/irq-imx-mu-msi.c:14:10: fatal error: linux/dma-iommu.h: No such file or directory
> 14 | #include <linux/dma-iommu.h>
> | ^~~~~~~~~~~~~~~~~~~
>
> Caused by commit
>
> 841e6e9f2bc95baff ("irqchip: Add IMX MU MSI controller driver")
>
> interacting with
>
> f2042ed21da7f8886 ("iommu/dma: Make header private")
>
> I have reverted the driver for today.
Once again it looks like an unused include which could just be
removed... illustrating a large part of why I took the header away :)
Cheers,
Robin.
next prev parent reply other threads:[~2022-09-29 14:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 14:31 linux-next: build failure after merge of the irqchip tree broonie
2022-09-29 14:40 ` Robin Murphy [this message]
2022-09-29 16:22 ` Marc Zyngier
-- strict thread matches above, loose matches on Subject: below --
2022-07-11 5:42 Stephen Rothwell
2022-07-11 8:15 ` Marc Zyngier
2022-07-08 4:13 Stephen Rothwell
2022-07-08 7:48 ` Marc Zyngier
2021-06-22 4:15 Stephen Rothwell
2021-04-08 6:35 Stephen Rothwell
2021-04-08 7:56 ` Marc Zyngier
2021-04-08 8:35 ` Jonathan Neuschäfer
2020-03-23 6:59 Stephen Rothwell
2020-03-23 8:08 ` Michal Simek
2020-03-26 6:36 ` Stephen Rothwell
2020-03-26 7:06 ` Michal Simek
2018-10-08 3:06 Stephen Rothwell
2018-10-08 7:06 ` Marc Zyngier
2015-04-13 7:05 Stephen Rothwell
2015-04-13 9:10 ` Stefan Agner
2015-04-13 10:50 ` Jason Cooper
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=7f9d35bf-282f-68cf-b857-3d7e66dbaf63@arm.com \
--to=robin.murphy@arm$(echo .)com \
--cc=Frank.Li@nxp$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=iommu@lists$(echo .)linux.dev \
--cc=jroedel@suse$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=maz@kernel$(echo .)org \
--cc=will@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