Thread (3 messages) 3 messages, 2 authors, 2017-08-26

[PATCH] iommu/mediatek: Fix a build fail of m4u_type

From: matthias.bgg@gmail.com (Matthias Brugger)
Date: 2017-08-26 18:46:20
Also in: linux-devicetree, linux-iommu, linux-mediatek, lkml


On 08/26/2017 09:33 PM, Matthias Brugger wrote:

On 08/24/2017 08:24 AM, Yong Wu wrote:
quoted
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':
quoted
quoted
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 <redacted>
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
---
1) In the v2 of mt2712 iommu support patch-set, We changed a variant
name from "m4u_type" to "m4u_plat", But I'm sorry that I forgot to
change it in the later patch.
2) This patch is based on [1].
[1]:https://lists.linuxfoundation.org/pipermail/iommu/2017-August/023847.html
3) I cann't find the commit id of the patch ("iommu/mediatek: Enlarge
the validate PA range for 4GB mode") in the [2].
So I don't write the commit id for that patch in the commit message.
[2]https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git next
Because the kernel test robot took the patch from the mailinglist. Please fold 
this fix into v3 of the series.
Please ignore this message, I didn't realize that the driver was already queued 
by Joerg.

Regards,
Matthias
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help