All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: broonie@kernel.org, Joerg Roedel <jroedel@suse.de>,
	Frank Li <Frank.Li@nxp.com>, Will Deacon <will@kernel.org>,
	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 17:22:38 +0100	[thread overview]
Message-ID: <86czbe6tgx.wl-maz@kernel.org> (raw)
In-Reply-To: <7f9d35bf-282f-68cf-b857-3d7e66dbaf63@arm.com>

On Thu, 29 Sep 2022 15:40:56 +0100,
Robin Murphy <robin.murphy@arm.com> wrote:
> 
> 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 :)

Thanks both. I've now fixed the driver by dropping this include (and
another one) and pushed the -next branch out again.

	M.

-- 
Without deviation from the norm, progress is not possible.

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: broonie@kernel.org, Joerg Roedel <jroedel@suse.de>,
	Frank Li <Frank.Li@nxp.com>, Will Deacon <will@kernel.org>,
	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 17:22:38 +0100	[thread overview]
Message-ID: <86czbe6tgx.wl-maz@kernel.org> (raw)
In-Reply-To: <7f9d35bf-282f-68cf-b857-3d7e66dbaf63@arm.com>

On Thu, 29 Sep 2022 15:40:56 +0100,
Robin Murphy <robin.murphy@arm.com> wrote:
> 
> 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 :)

Thanks both. I've now fixed the driver by dropping this include (and
another one) and pushed the -next branch out again.

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-09-29 16:22 UTC|newest]

Thread overview: 24+ 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:31 ` broonie
2022-09-29 14:40 ` Robin Murphy
2022-09-29 14:40   ` Robin Murphy
2022-09-29 16:22   ` Marc Zyngier [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-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=86czbe6tgx.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=broonie@kernel.org \
    --cc=iommu@lists.linux.dev \
    --cc=jroedel@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@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 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.