From: "'Joerg Roedel'" <joro@8bytes.org>
To: Kukjin Kim <kgene.kim@samsung.com>
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 19:38:23 +0100 [thread overview]
Message-ID: <20130110183823.GH25591@8bytes.org> (raw)
In-Reply-To: <026e01cdef5d$364fd150$a2ef73f0$@samsung.com>
On Thu, Jan 10, 2013 at 10:06:24AM -0800, Kukjin Kim wrote:
> 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.
I would like to take the final version of this patch-set (when you
provided your Acked-by) into the arm/exynos branch in my tree. You can
then pull in this branch to the Samsung tree and we can the conflicts
this way.
Joerg
next prev parent reply other threads:[~2013-01-10 18:38 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' [this message]
2013-01-10 18:34 ` Kukjin Kim
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=20130110183823.GH25591@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kgene.kim@samsung.com \
--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