[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170830131852.lpkixnpt2ei4lpka@8bytes.org>
Date: Wed, 30 Aug 2017 15:18:52 +0200
From: Joerg Roedel <joro@...tes.org>
To: Arvind Yadav <arvind.yadav.cs@...il.com>
Cc: m.szyprowski@...sung.com, kgene@...nel.org, krzk@...nel.org,
matthias.bgg@...il.com, gerald.schaefer@...ibm.com,
linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH 2/3] iommu: mtk: constify iommu_ops
On Mon, Aug 28, 2017 at 05:42:26PM +0530, Arvind Yadav wrote:
> iommu_ops are not supposed to change at runtime.
> Functions 'iommu_device_set_ops' and 'bus_set_iommu' working with
> const iommu_ops provided by <linux/iommu.h>. So mark the non-const
> structs as const.
>
> Signed-off-by: Arvind Yadav <arvind.yadav.cs@...il.com>
> ---
> drivers/iommu/mtk_iommu.c | 4 ++--
> drivers/iommu/mtk_iommu_v1.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
This doesn't apply cleanly to the arm/mediatek branch in the iommu-tree.
Please rebase it against that branch and update the subject to:
iommu/mediatek: Constify iommu_ops
to match the convention used in the iommu-tree and send it again.
Thanks,
Joerg
Powered by blists - more mailing lists