All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yong Wu <yong.wu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
To: Arvind Yadav <arvind.yadav.cs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: RE: [PATCH 2/3] iommu: mtk: constify iommu_ops
Date: Mon, 10 Sep 2018 10:35:34 +0800	[thread overview]
Message-ID: <1536546934.29639.4.camel@mhfsdcap03> (raw)
In-Reply-To: <d7decc0805d04c148bb2cbda8b70b767-1/hHtGjKHHyGRgb7Xm6L22/AB3i2Q03W@public.gmane.org>

Hi Arvind,

     This patch looks lost. Could you help resend it after changing the
title to "iommu/mediatek:xxx"?

Thanks.

On Fri, 2018-09-07 at 14:21 +0800, Yong Wu (吴勇) wrote:
> From: Linux-mediatek [mailto:linux-mediatek-bounces@lists.infradead.org] On Behalf Of Arvind Yadav
> Sent: Monday, August 28, 2017 8:12 PM
> To: m.szyprowski@samsung.com; joro@8bytes.org; kgene@kernel.org; krzk@kernel.org; matthias.bgg@gmail.com; gerald.schaefer@de.ibm.com
> Cc: iommu@lists.linux-foundation.org; linux-mediatek@lists.infradead.org; linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org
> Subject: [PATCH 2/3] iommu: mtk: constify iommu_ops
> 
> 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@gmail.com>
> ---
>  drivers/iommu/mtk_iommu.c    | 4 ++--
>  drivers/iommu/mtk_iommu_v1.c | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/iommu/mtk_iommu.c b/drivers/iommu/mtk_iommu.c index 91c6d36..eac99a3 100644
> --- a/drivers/iommu/mtk_iommu.c
> +++ b/drivers/iommu/mtk_iommu.c
> @@ -102,7 +102,7 @@ struct mtk_iommu_domain {
>  	struct iommu_domain		domain;
>  };
>  
> -static struct iommu_ops mtk_iommu_ops;
> +static const struct iommu_ops mtk_iommu_ops;
>  
>  static struct mtk_iommu_domain *to_mtk_domain(struct iommu_domain *dom)  { @@ -437,7 +437,7 @@ static int mtk_iommu_of_xlate(struct device *dev, struct of_phandle_args *args)
>  	return iommu_fwspec_add_ids(dev, args->args, 1);  }
>  
> -static struct iommu_ops mtk_iommu_ops = {
> +static const struct iommu_ops mtk_iommu_ops = {
>  	.domain_alloc	= mtk_iommu_domain_alloc,
>  	.domain_free	= mtk_iommu_domain_free,
>  	.attach_dev	= mtk_iommu_attach_device,
> diff --git a/drivers/iommu/mtk_iommu_v1.c b/drivers/iommu/mtk_iommu_v1.c index bc1efbf..40b231f 100644
> --- a/drivers/iommu/mtk_iommu_v1.c
> +++ b/drivers/iommu/mtk_iommu_v1.c
> @@ -363,7 +363,7 @@ static phys_addr_t mtk_iommu_iova_to_phys(struct iommu_domain *domain,
>  	return pa;
>  }
>  
> -static struct iommu_ops mtk_iommu_ops;
> +static const struct iommu_ops mtk_iommu_ops;
>  
>  /*
>   * MTK generation one iommu HW only support one iommu domain, and all the client @@ -536,7 +536,7 @@ static int mtk_iommu_hw_init(const struct mtk_iommu_data *data)
>  	return 0;
>  }
>  
> -static struct iommu_ops mtk_iommu_ops = {
> +static const struct iommu_ops mtk_iommu_ops = {
>  	.domain_alloc	= mtk_iommu_domain_alloc,
>  	.domain_free	= mtk_iommu_domain_free,
>  	.attach_dev	= mtk_iommu_attach_device,
> --
> 1.9.1
> 
> 
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek


_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  parent reply	other threads:[~2018-09-10  2:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <80e3d51296564c929a039ac83d83dd94@mtkmbs01n1.mediatek.inc>
     [not found] ` <80e3d51296564c929a039ac83d83dd94-fSWMoTp6f3O9JaaB6nfwCW/AB3i2Q03W@public.gmane.org>
2017-08-29  5:43   ` FW: [PATCH 2/3] iommu: mtk: constify iommu_ops Yong Wu
     [not found] ` <d7decc0805d04c148bb2cbda8b70b767@MTKMBS31N1.mediatek.inc>
     [not found]   ` <d7decc0805d04c148bb2cbda8b70b767-1/hHtGjKHHyGRgb7Xm6L22/AB3i2Q03W@public.gmane.org>
2018-09-10  2:35     ` Yong Wu [this message]
2017-08-28 12:12 Arvind Yadav
2017-08-28 12:12 ` Arvind Yadav
2017-08-30 13:18 ` Joerg Roedel
2017-08-30 13:18   ` Joerg Roedel
2017-08-30 13:18   ` 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=1536546934.29639.4.camel@mhfsdcap03 \
    --to=yong.wu-nus5lvnupcjwk0htik3j/w@public.gmane.org \
    --cc=arvind.yadav.cs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.