From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Joerg Roedel'" <joro@8bytes.org>
Cc: "'Cho KyongHo'" <pullip.cho@samsung.com>,
"'Linux ARM Kernel'" <linux-arm-kernel@lists.infradead.org>,
"'Linux IOMMU'" <iommu@lists.linux-foundation.org>,
"'Linux Kernel'" <linux-kernel@vger.kernel.org>,
"'Linux Samsung SOC'" <linux-samsung-soc@vger.kernel.org>,
"'Hyunwoong Kim'" <khw0178.kim@samsung.com>,
"'Prathyush'" <prathyush.k@samsung.com>,
"'Rahul Sharma'" <rahul.sharma@samsung.com>,
"'Subash Patel'" <supash.ramaswamy@linaro.org>
Subject: RE: [PATCH v6 00/12] iommu/exynos: Fixes and Enhancements of System MMU driver with DT
Date: Thu, 10 Jan 2013 10:34:48 -0800 [thread overview]
Message-ID: <027601cdef61$2df576a0$89e063e0$@samsung.com> (raw)
In-Reply-To:
Kukjin Kim wrote:
>
> 'Joerg Roedel' wrote:
> >
> > On Mon, Dec 31, 2012 at 10:18:46AM -0800, Kukjin Kim wrote:
> > > Cho KyongHo wrote:
> >
> > > > Diffstats:
> > > > arch/arm/boot/dts/exynos5250-smdk5250.dts | 2 +-
> > > > arch/arm/boot/dts/exynos5250.dtsi | 27 +-
> > > > arch/arm/mach-exynos/Kconfig | 5 -
> > > > arch/arm/mach-exynos/Makefile | 1 -
> > > > arch/arm/mach-exynos/clock-exynos4.c | 41 +-
> > > > arch/arm/mach-exynos/clock-exynos4210.c | 9 +-
> > > > arch/arm/mach-exynos/clock-exynos4212.c | 23 +-
> > > > arch/arm/mach-exynos/clock-exynos5.c | 87 +-
> > > > arch/arm/mach-exynos/dev-sysmmu.c | 274 ------
> > > > arch/arm/mach-exynos/include/mach/sysmmu.h | 66 --
> > > > arch/arm/mach-exynos/mach-exynos4-dt.c | 34 +
> > > > arch/arm/mach-exynos/mach-exynos5-dt.c | 30 +
> > > > drivers/iommu/Kconfig | 2 +-
> > > > drivers/iommu/Makefile | 2 +-
> > > > drivers/iommu/exynos-iommu.c | 1477
> > +++++++++++++++++++++--
> > > > -----
> > > > 15 files changed, 1284 insertions(+), 796 deletions(-)
> > >
> > > Joerg, it's time to merge this. If you don't mind, let me pick up this
whole
> > > series into Samsung tree because this touches many Samsung stuff.
> >
> > Well, looking at the diffstat the IOMMU changes are a lot larger than
> > the exynos ones. So I think this should go through the IOMMU tree once
> > the latest review comments are fixed.
> >
> If so, too many ugly merge conflicts will be happened when Linus merges
for
> v3.9 because the legacy(current) exynos clock stuff is going away in
Samsung
> tree and as I said, this touches Samsung stuff widely. Of course, Stephen
> should complain the conflicts between your tree and mine once you apply
> this whole series in your -next before Linus' merge for v3.9. I believe,
you
> don't want it.
>
> You know, we have several options to avoid it. When you take this series
in
> your tree, you can provide topic branch for me. Or this series should be
> separated for arch/arm/ and drivers/ for both trees, then only
> drivers/iommu changes should be picked up in your tree. I'm OK both, let
me
> know which one you would prefer or other way.
>
Hmm, I think, just one [7/12] patch does matter so if you could create topic
branch and apply [7/12] patch firstly before other drivers/ changes would be
better to me. It's OK on both trees if I just _merge_ the first [7/12]
commit in the topic branch you provided for exynos-iommu. But you know, you
don't have to rebase it once I merge it in Samsung tree.
How about?
> BTW, KyongHo, you need to update the clock changes for exynos-iommu
> against on exynos common clock stuff.
>
KyoungHo, your changes don't matter on exynos common clock stuff and I can
take care in my tree. So no need more work for it in your side. If any
updates, let you know.
Thanks.
- Kukjin
next prev parent reply other threads:[~2013-01-10 18:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 1:53 Cho KyongHo
2012-12-31 18:18 ` Kukjin Kim
2013-01-10 17:19 ` 'Joerg Roedel'
2013-01-10 18:06 ` Kukjin Kim
2013-01-10 18:38 ` 'Joerg Roedel'
2013-01-10 18:34 ` Kukjin Kim [this message]
2013-01-10 19:12 ` 'Joerg Roedel'
2013-01-10 19:33 ` Kukjin Kim
2013-01-11 15:52 ` 'Joerg Roedel'
2013-01-03 23:18 ` Sylwester Nawrocki
[not found] ` <CAHQjnOMxYo1D6EgX6ZnGBm_Ufr+u4hgKQzAyQdXJGhiC3XpKdA@mail.gmail.com>
2013-01-08 22:23 ` Sylwester Nawrocki
2013-01-16 16:57 ` KyongHo Cho
2013-01-16 10:53 ` Will Deacon
2013-01-16 17:00 ` KyongHo Cho
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='027601cdef61$2df576a0$89e063e0$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=khw0178.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=prathyush.k@samsung.com \
--cc=pullip.cho@samsung.com \
--cc=rahul.sharma@samsung.com \
--cc=supash.ramaswamy@linaro.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
Powered by JetHome