From: Tony Lindgren <tony@atomide.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-arm-kernel@lists.infradead.org,
Ohad Ben-Cohen <ohad@wizery.com>,
Joerg Roedel <joerg.roedel@amd.com>,
linux-omap@vger.kernel.org, Ido Yariv <ido@wizery.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [PATCH 3/4] ARM: OMAP2+: Move iommu/iovmm headers to platform_data
Date: Thu, 18 Oct 2012 13:30:29 -0700 [thread overview]
Message-ID: <20121018203028.GE30550@atomide.com> (raw)
In-Reply-To: <20121018162512.GD30550@atomide.com>
* Tony Lindgren <tony@atomide.com> [121018 09:27]:
> * Laurent Pinchart <laurent.pinchart@ideasonboard.com> [121018 06:45]:
> > Hi,
> >
> > On Monday 15 October 2012 17:36:40 Tony Lindgren wrote:
> > > From: Ido Yariv <ido@wizery.com>
> > >
> > > Move iommu/iovmm headers from plat/ to platform_data/ as part of the
> > > single zImage work.
> >
> > Is that really where those headers belong ? iommu-omap.h contains far more
> > than platform data, and iovmm-omap.h contains no platform data at all.
>
> Hmm I though that was already fixed by Ido but looks like there are
> non-platform data things still remaining there.
>
> Looking at arch/arm/mach-omap2/iommu2.c it seems that it should moved to
> drivers/iommu/omap-iommu2.c and that way most of the header can be local
> in drivers/iommu/omap-iommu.h. I'll do some patches for that and repost.
I ended up solving the iovmm-omap.h issue by adding include/linux/omap-iommu.h
like intel and amd have.
Reposted the series as "[PATCH v3 0/6] omap iommu changes to remove plat includes".
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] ARM: OMAP2+: Move iommu/iovmm headers to platform_data
Date: Thu, 18 Oct 2012 13:30:29 -0700 [thread overview]
Message-ID: <20121018203028.GE30550@atomide.com> (raw)
In-Reply-To: <20121018162512.GD30550@atomide.com>
* Tony Lindgren <tony@atomide.com> [121018 09:27]:
> * Laurent Pinchart <laurent.pinchart@ideasonboard.com> [121018 06:45]:
> > Hi,
> >
> > On Monday 15 October 2012 17:36:40 Tony Lindgren wrote:
> > > From: Ido Yariv <ido@wizery.com>
> > >
> > > Move iommu/iovmm headers from plat/ to platform_data/ as part of the
> > > single zImage work.
> >
> > Is that really where those headers belong ? iommu-omap.h contains far more
> > than platform data, and iovmm-omap.h contains no platform data at all.
>
> Hmm I though that was already fixed by Ido but looks like there are
> non-platform data things still remaining there.
>
> Looking at arch/arm/mach-omap2/iommu2.c it seems that it should moved to
> drivers/iommu/omap-iommu2.c and that way most of the header can be local
> in drivers/iommu/omap-iommu.h. I'll do some patches for that and repost.
I ended up solving the iovmm-omap.h issue by adding include/linux/omap-iommu.h
like intel and amd have.
Reposted the series as "[PATCH v3 0/6] omap iommu changes to remove plat includes".
Regards,
Tony
next prev parent reply other threads:[~2012-10-18 20:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 0:36 [PATCH 0/4] repost of the omap iommu header changes to remove plat includes Tony Lindgren
2012-10-16 0:36 ` Tony Lindgren
2012-10-16 0:36 ` [PATCH 1/4] ARM: OMAP: Merge iommu2.h into iommu.h Tony Lindgren
2012-10-16 0:36 ` Tony Lindgren
2012-10-16 0:36 ` [PATCH 2/4] ARM: OMAP2+: Make some definitions local Tony Lindgren
2012-10-16 0:36 ` Tony Lindgren
2012-10-16 0:36 ` [PATCH 3/4] ARM: OMAP2+: Move iommu/iovmm headers to platform_data Tony Lindgren
2012-10-16 0:36 ` Tony Lindgren
2012-10-16 0:38 ` Tony Lindgren
2012-10-16 0:38 ` Tony Lindgren
2012-10-18 13:44 ` Laurent Pinchart
2012-10-18 13:44 ` Laurent Pinchart
2012-10-18 16:25 ` Tony Lindgren
2012-10-18 16:25 ` Tony Lindgren
2012-10-18 20:30 ` Tony Lindgren [this message]
2012-10-18 20:30 ` Tony Lindgren
2012-10-16 0:36 ` [PATCH 4/4] ARM: OMAP2+: Move iopgtable header to drivers/iommu/ Tony Lindgren
2012-10-16 0:36 ` Tony Lindgren
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=20121018203028.GE30550@atomide.com \
--to=tony@atomide.com \
--cc=ido@wizery.com \
--cc=joerg.roedel@amd.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=ohad@wizery.com \
/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.