From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] iommu/mediatek: Fix a build fail of m4u_type
Date: Mon, 28 Aug 2017 11:26:42 +0200 [thread overview]
Message-ID: <20170828092641.mrr2qynqwxhrwhjb@8bytes.org> (raw)
In-Reply-To: <1503560532-24416-1-git-send-email-yong.wu@mediatek.com>
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@intel.com>
> Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Applied both, thanks.
prev parent reply other threads:[~2017-08-28 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 7:42 [PATCH v2 1/2] iommu/mediatek: Fix a build fail of m4u_type Yong Wu
2017-08-24 7:42 ` [PATCH v2 2/2] iommu/mediatek: Fix a build warning of BIT(32) in ARM Yong Wu
2017-08-28 9:26 ` Joerg Roedel [this message]
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=20170828092641.mrr2qynqwxhrwhjb@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).