public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brown <davidb@codeaurora.org>
To: Ohad Ben-Cohen <ohad@wizery.com>, stepanm@codeaurora.org
Cc: Arnd Bergmann <arnd@arndb.de>,
	Joerg Roedel <Joerg.Roedel@amd.com>,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	linux-pci@vger.kernel.org, linux-omap@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] msm: iommu: move to drivers/iommu/
Date: Wed, 08 Jun 2011 15:27:10 -0700	[thread overview]
Message-ID: <8yamxhsklhd.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <1307522062-19273-3-git-send-email-ohad@wizery.com> (Ohad Ben-Cohen's message of "Wed, 8 Jun 2011 11:34:20 +0300")

On Wed, Jun 08 2011, Ohad Ben-Cohen wrote:

> This should ease finding similarities with different platforms,
> with the intention of solving problems once in a generic framework
> which everyone can use.
>
> Compile-tested for MSM8X60.
>
> Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
> ---
>  arch/arm/mach-msm/Kconfig                          |   12 ------------
>  arch/arm/mach-msm/Makefile                         |    2 +-
>  drivers/iommu/Kconfig                              |   11 +++++++++++
>  drivers/iommu/Makefile                             |    1 +
>  .../mach-msm/iommu.c => drivers/iommu/msm-iommu.c  |    0
>  5 files changed, 13 insertions(+), 13 deletions(-)
>  rename arch/arm/mach-msm/iommu.c => drivers/iommu/msm-iommu.c (100%)

Moving the driver is good.  I'm wondering what we should do with
iommu_dev.c, though.  Wouldn't it make sense to move this file as well?

I've added the author, Stepan Moskovchenko, in case he has any feedback.

David

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2011-06-08 22:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  8:34 [PATCH 0/4] drivers/iommu/ relocations Ohad Ben-Cohen
2011-06-08  8:34 ` [PATCH 1/4] drivers: iommu: move to a dedicated folder Ohad Ben-Cohen
2011-06-08  8:34 ` [PATCH 2/4] msm: iommu: move to drivers/iommu/ Ohad Ben-Cohen
2011-06-08 22:27   ` David Brown [this message]
2011-06-10 16:24     ` Ohad Ben-Cohen
2011-06-08  8:34 ` [PATCH 3/4] x86: amd_iommu: " Ohad Ben-Cohen
2011-06-08  8:34 ` [PATCH 4/4] x86: intel-iommu: " Ohad Ben-Cohen
2011-06-08  9:17   ` David Woodhouse
2011-06-08  9:38     ` Roedel, Joerg
2011-06-08 10:33     ` Ohad Ben-Cohen
2011-06-08 17:47   ` Chris Wright
2011-06-08 19:35     ` Ohad Ben-Cohen
2011-06-08  9:35 ` [PATCH 0/4] drivers/iommu/ relocations Roedel, Joerg
2011-06-08 14:32   ` Ingo Molnar
2011-06-08 22:23   ` David Brown
2011-06-08 13:05 ` Matthew Wilcox
2011-06-08 13:11   ` Ohad Ben-Cohen
2011-06-08 13:35     ` Roedel, Joerg

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=8yamxhsklhd.fsf@huya.qualcomm.com \
    --to=davidb@codeaurora.org \
    --cc=Joerg.Roedel@amd.com \
    --cc=arnd@arndb.de \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=stepanm@codeaurora.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