Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <7f9d35bf-282f-68cf-b857-3d7e66dbaf63@arm.com>
Date:   Thu, 29 Sep 2022 15:40:56 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101
 Thunderbird/102.3.0
Subject: Re: linux-next: build failure after merge of the irqchip tree
Content-Language: en-GB
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
References: <20220929143149.126145-1-broonie@kernel.org>
From:   Robin Murphy <robin.murphy@arm.com>
In-Reply-To: <20220929143149.126145-1-broonie@kernel.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.