[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170828092641.mrr2qynqwxhrwhjb@8bytes.org>
Date: Mon, 28 Aug 2017 11:26:42 +0200
From: Joerg Roedel <joro@...tes.org>
To: Yong Wu <yong.wu@...iatek.com>
Cc: Matthias Brugger <matthias.bgg@...il.com>,
Robin Murphy <robin.murphy@....com>,
Will Deacon <will.deacon@....com>,
Daniel Kurtz <djkurtz@...gle.com>,
Tomasz Figa <tfiga@...gle.com>,
Rob Herring <robh+dt@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
linux-mediatek@...ts.infradead.org, srv_heupstream@...iatek.com,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
iommu@...ts.linux-foundation.org, arnd@...db.de,
honghui.zhang@...iatek.com
Subject: Re: [PATCH v2 1/2] iommu/mediatek: Fix a build fail of m4u_type
On Thu, Aug 24, 2017 at 03:42:11PM +0800, Yong Wu wrote:
> The commit ("iommu/mediatek: Enlarge the validate PA range
> for 4GB mode") introduce the following build error:
>
> drivers/iommu/mtk_iommu.c: In function 'mtk_iommu_hw_init':
> >> drivers/iommu/mtk_iommu.c:536:30: error: 'const struct mtk_iommu_data'
> has no member named 'm4u_type'; did you mean 'm4u_dom'?
> if (data->enable_4GB && data->m4u_type != M4U_MT8173) {
>
> This patch fix it, use "m4u_plat" instead of "m4u_type".
>
> Reported-by: kernel test robot <lkp@...el.com>
> Signed-off-by: Yong Wu <yong.wu@...iatek.com>
Applied both, thanks.
Powered by blists - more mailing lists