All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Joerg Roedel <joro@8bytes.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Sven Peter <sven@svenpeter.dev>
Subject: Re: linux-next: build failure after merge of the iommu tree
Date: Tue, 12 Oct 2021 09:33:48 +0100	[thread overview]
Message-ID: <87ily2prpv.wl-maz@kernel.org> (raw)
In-Reply-To: <20211012144639.0af3457c@canb.auug.org.au>

[+ Sven]

On Tue, 12 Oct 2021 04:46:39 +0100,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Hi all,
> 
> After merging the iommu tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/iommu/apple-dart.c: In function 'apple_dart_get_resv_regions':
> drivers/iommu/apple-dart.c:758:2: error: implicit declaration of function 'iommu_dma_get_resv_regions'; did you mean 'iommu_get_resv_regions'? [-Werror=implicit-function-declaration]
>   758 |  iommu_dma_get_resv_regions(dev, head);
>       |  ^~~~~~~~~~~~~~~~~~~~~~~~~~
>       |  iommu_get_resv_regions
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>   b2b2781a9755 ("iommu/dart: Clean up IOVA cookie crumbs")
> 
> interactig with commit
> 
>   05dc551614a4 ("iommu/dart: Exclude MSI doorbell from PCIe device IOVA range")
> 
> from the pci tree.
> 
> I have applied the following merge fix patch.
> 
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 12 Oct 2021 14:40:49 +1100
> Subject: [PATCH] fix for "iommu/dart: Exclude MSI doorbell from PCIe device
>  IOVA range"
> 
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>  drivers/iommu/apple-dart.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/iommu/apple-dart.c b/drivers/iommu/apple-dart.c
> index 912be9b7669c..280ff8df728d 100644
> --- a/drivers/iommu/apple-dart.c
> +++ b/drivers/iommu/apple-dart.c
> @@ -15,6 +15,7 @@
>  #include <linux/bitfield.h>
>  #include <linux/clk.h>
>  #include <linux/dev_printk.h>
> +#include <linux/dma-iommu.h>
>  #include <linux/dma-mapping.h>
>  #include <linux/err.h>
>  #include <linux/interrupt.h>

Thanks for fixing this. Lorenzo, do you mind slapping this on top of
the Apple PCIe series?

Thanks,

	M.

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

  reply	other threads:[~2021-10-12  8:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12  3:46 linux-next: build failure after merge of the iommu tree Stephen Rothwell
2021-10-12  8:33 ` Marc Zyngier [this message]
2021-10-12 11:21   ` Lorenzo Pieralisi
2021-10-13  1:43     ` Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2026-01-19 18:42 Mark Brown
2026-01-20  9:17 ` Joerg Roedel
2020-09-21  4:09 Stephen Rothwell
2020-09-21  4:09 ` Stephen Rothwell
2020-10-13  7:31 ` Stephen Rothwell
2020-10-13  7:31   ` Stephen Rothwell
2020-10-15  2:43   ` Stephen Rothwell
2020-10-15  2:43     ` Stephen Rothwell
2019-09-02  6:39 Stephen Rothwell
2019-09-02 14:03 ` Joerg Roedel
2019-09-02 14:26   ` Lendacky, Thomas
2019-09-03  5:28     ` Stephen Rothwell
2015-11-01 11:42 Stephen Rothwell
2015-11-01 15:14 ` Joerg Roedel
2015-11-02  0:15   ` Magnus Damm
2014-11-05  2:47 Stephen Rothwell
2014-11-05  2:47 ` Stephen Rothwell
2014-11-05 11:16 ` Joerg Roedel
2014-11-05 11:16   ` Joerg Roedel
2014-07-08  4:02 Stephen Rothwell
2014-07-08  4:12 ` Alex Williamson
2014-07-08 11:20 ` Joerg Roedel
2011-12-15  4:40 Stephen Rothwell
2011-12-15 10:09 ` Joerg Roedel
2011-08-29  3:32 Stephen Rothwell
2011-08-29  5:11 ` Ohad Ben-Cohen
2011-08-29 10:42   ` Joerg Roedel
2011-08-29  8:36 ` 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=87ily2prpv.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=robin.murphy@arm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sven@svenpeter.dev \
    /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.