linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Joerg.Roedel@amd.com (Roedel, Joerg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 5/5] iommu/exynos: Use bus_set_iommu instead of register_iommu
Date: Fri, 30 Sep 2011 15:46:43 +0200	[thread overview]
Message-ID: <20110930134643.GS2138@amd.com> (raw)
In-Reply-To: <017001cc7f43$04a2db60$0de89220$%kim@samsung.com>

On Fri, Sep 30, 2011 at 03:31:49AM -0400, Kukjin Kim wrote:
> From: KyongHo Cho <pullip.cho@samsung.com>
> 
> This replaces register_iommu() with bus_set_iommu() according to the
> suggestion of Joerg Roedel.

This should be part of patch 3 already when the bus_set_iommu() change
is merged. Otherwise it breaks bisectability too.

	Joerg

> 
> Cc: Joerg Roedel <joerg.roedel@amd.com>
> Signed-off-by: KyongHo Cho <pullip.cho@samsung.com>
> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
> ---
>  drivers/iommu/exynos_iommu.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/iommu/exynos_iommu.c b/drivers/iommu/exynos_iommu.c
> index d355a2e..e36f7b2 100644
> --- a/drivers/iommu/exynos_iommu.c
> +++ b/drivers/iommu/exynos_iommu.c
> @@ -912,7 +912,7 @@ static int __init exynos_iommu_init(void)
>  	if (!l2table_cachep)
>  		return -ENOMEM;
>  
> -	register_iommu(&exynos_iommu_ops);
> +	bus_set_iommu(&platform_bus_type, &exynos_iommu_ops);
>  
>  	return 0;
>  }
> -- 
> 1.7.1
> 
> 

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632

  reply	other threads:[~2011-09-30 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30  7:31 [PATCH v2 5/5] iommu/exynos: Use bus_set_iommu instead of register_iommu Kukjin Kim
2011-09-30 13:46 ` Roedel, Joerg [this message]
2011-09-30 23:52   ` KyongHo Cho
2011-10-07 11:37     ` 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=20110930134643.GS2138@amd.com \
    --to=joerg.roedel@amd.com \
    --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).