From: Joerg Roedel <joro@8bytes.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Olav Haugan <ohaugan@codeaurora.org>,
ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: build failure after merge of the iommu tree
Date: Wed, 5 Nov 2014 12:16:56 +0100 [thread overview]
Message-ID: <20141105111656.GJ10744@8bytes.org> (raw)
In-Reply-To: <20141105134731.799a1a3d@canb.auug.org.au>
On Wed, Nov 05, 2014 at 01:47:31PM +1100, Stephen Rothwell wrote:
> Hi Joerg,
>
> After merging the iommu tree, today's linux-next build (powerpc
> pc64_defconfig) failed like this:
>
> In file included from arch/powerpc/platforms/powernv/pci.c:33:0:
> arch/powerpc/include/asm/iommu.h:140:12: error: conflicting types for 'iommu_map_sg'
> extern int iommu_map_sg(struct device *dev, struct iommu_table *tbl,
> ^
> In file included from arch/powerpc/platforms/powernv/pci.c:23:0:
> include/linux/iommu.h:311:22: note: previous definition of 'iommu_map_sg' was here
> static inline size_t iommu_map_sg(struct iommu_domain *domain,
> ^
>
> Caused by commit 315786ebbf4a ("iommu: Add iommu_map_sg() function").
> Grep is your friend ...
>
> I have used the iommu tree from next-20141104 for today.
Thanks Stephen, I exluded the my core branch from next for now until the
issue is fixed.
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olav Haugan <ohaugan@codeaurora.org>,
linux-next@vger.kernel.org,
ppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the iommu tree
Date: Wed, 5 Nov 2014 12:16:56 +0100 [thread overview]
Message-ID: <20141105111656.GJ10744@8bytes.org> (raw)
In-Reply-To: <20141105134731.799a1a3d@canb.auug.org.au>
On Wed, Nov 05, 2014 at 01:47:31PM +1100, Stephen Rothwell wrote:
> Hi Joerg,
>
> After merging the iommu tree, today's linux-next build (powerpc
> pc64_defconfig) failed like this:
>
> In file included from arch/powerpc/platforms/powernv/pci.c:33:0:
> arch/powerpc/include/asm/iommu.h:140:12: error: conflicting types for 'iommu_map_sg'
> extern int iommu_map_sg(struct device *dev, struct iommu_table *tbl,
> ^
> In file included from arch/powerpc/platforms/powernv/pci.c:23:0:
> include/linux/iommu.h:311:22: note: previous definition of 'iommu_map_sg' was here
> static inline size_t iommu_map_sg(struct iommu_domain *domain,
> ^
>
> Caused by commit 315786ebbf4a ("iommu: Add iommu_map_sg() function").
> Grep is your friend ...
>
> I have used the iommu tree from next-20141104 for today.
Thanks Stephen, I exluded the my core branch from next for now until the
issue is fixed.
Joerg
next prev parent reply other threads:[~2014-11-05 11:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 2:47 linux-next: build failure after merge of the iommu tree Stephen Rothwell
2014-11-05 2:47 ` Stephen Rothwell
2014-11-05 11:16 ` Joerg Roedel [this message]
2014-11-05 11:16 ` Joerg Roedel
-- strict thread matches above, loose matches on Subject: below --
2026-01-19 18:42 Mark Brown
2026-01-20 9:17 ` Joerg Roedel
2021-10-12 3:46 Stephen Rothwell
2021-10-12 8:33 ` Marc Zyngier
2021-10-12 11:21 ` Lorenzo Pieralisi
2021-10-13 1:43 ` Bjorn Helgaas
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-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=20141105111656.GJ10744@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ohaugan@codeaurora.org \
--cc=sfr@canb.auug.org.au \
/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.