From: Marek Szyprowski <m.szyprowski@samsung.com>
To: pullip.cho@samsung.com, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Cc: 'Joerg Roedel' <joro@8bytes.org>,
'Sanghyun Lee' <sanghyun75.lee@samsung.com>,
'Kukjin Kim' <kgene.kim@samsung.com>,
'Younglak Kim' <younglak1004.kim@samsung.com>,
'Kyungmin Park' <kyungmin.park@samsung.com>,
'Subash Patel' <subash.ramaswamy@linaro.org>
Subject: RE: [PATCH v9 0/2] iommu/exynos: Add IOMMU/System MMU driver for Samsung Exynos
Date: Thu, 01 Mar 2012 11:40:27 +0100 [thread overview]
Message-ID: <00fe01ccf797$b7ced690$276c83b0$%szyprowski@samsung.com> (raw)
In-Reply-To: <001801ccf5e3$69d79860$3d86c920$%cho@samsung.com>
Hi,
On Tuesday, February 28, 2012 7:37 AM KyongHo Cho wrote:
> Changes since v8:
> - exynos_iommu_map/unmap() just works for the page sizes
> that System MMU supports. (Joerg's comment)
> - 1 platform device for 1 H/W though a multimedia accelerator
> with several System MMUs attached.
> This make controlling System MMU simpler.
> - Information between System MMU and the accelerators:
> Shifted to accelerator's device structure from System MMU's
Could you tell which kernel tree did you use as a base for this patch?
It doesn't apply onto any of the known kernel trees (I've tried v3.2, v3.3-rc5 and
kgene/for-next). It looks that you have used some internal tree because cannot
find arch/arm/mach-exynos/clock-exynos5.c or arch/arm/mach-exynos/clock-exynos4212.c
files in any of the public git repositories.
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
prev parent reply other threads:[~2012-03-01 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 6:37 [PATCH v9 0/2] iommu/exynos: Add IOMMU/System MMU driver for Samsung Exynos KyongHo Cho
2012-02-28 7:01 ` Kyungmin Park
[not found] ` <CAH9JG2Vg8o_mm0gM042T0-kjMUoAdLzF+DeGErD7R86H0xqXZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-02 5:45 ` KyongHo Cho
2012-03-01 10:40 ` Marek Szyprowski [this message]
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='00fe01ccf797$b7ced690$276c83b0$%szyprowski@samsung.com' \
--to=m.szyprowski@samsung.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pullip.cho@samsung.com \
--cc=sanghyun75.lee@samsung.com \
--cc=subash.ramaswamy@linaro.org \
--cc=younglak1004.kim@samsung.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 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).