From: Kukjin Kim <kgene.kim@samsung.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
Subash Patel <subash.ramaswamy@linaro.org>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
"'Younglak Kim'" <younglak1004.kim@samsung.com>,
iommu@lists.linux-foundation.org,
"'Kyungmin Park'" <kyungmin.park@samsung.com>,
"'Sanghyun Lee'" <sanghyun75.lee@samsung.com>,
Cho KyongHo <pullip.cho@samsung.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v12 2/3] ARM: EXYNOS: Change System MMU platform device definitions
Date: Tue, 10 Apr 2012 12:34:35 -0700 [thread overview]
Message-ID: <4F848B4B.5000308@samsung.com> (raw)
In-Reply-To: <20120318132746.GL26973@8bytes.org>
Joerg Roedel wrote:
> On Fri, Mar 16, 2012 at 01:47:50PM -0700, Kukjin Kim wrote:
>> Anyway Joerg, how do you want to handle this? Do you want to pick up
>> 1/2/3 all of them in your tree? If so, 2nd patch should be on top of
>> some samsung topic stuff.
>
> Since patch 2 only applies to the Samsung tree, it is best to carry
> this in your tree for merging. Feel free to add my Acked-by to patch 3.
> But any further patches for the Exynos IOMMU drivers should go through
> my tree after it is merged.
>
Hi Joerg,
I applied 1st and 2nd patches in my tree.
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
next/cleanup-samsung-iommu
and my -next.
So please go ahead for 3rd patch in your tree. Note that if you need 1st
and 2nd patches for your tree, please merge the
'next/cleanup-samsung-iommu' branch in my tree. If not, will happen
useless conflicts.
If any problems, please let me know.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v12 2/3] ARM: EXYNOS: Change System MMU platform device definitions
Date: Tue, 10 Apr 2012 12:34:35 -0700 [thread overview]
Message-ID: <4F848B4B.5000308@samsung.com> (raw)
In-Reply-To: <20120318132746.GL26973@8bytes.org>
Joerg Roedel wrote:
> On Fri, Mar 16, 2012 at 01:47:50PM -0700, Kukjin Kim wrote:
>> Anyway Joerg, how do you want to handle this? Do you want to pick up
>> 1/2/3 all of them in your tree? If so, 2nd patch should be on top of
>> some samsung topic stuff.
>
> Since patch 2 only applies to the Samsung tree, it is best to carry
> this in your tree for merging. Feel free to add my Acked-by to patch 3.
> But any further patches for the Exynos IOMMU drivers should go through
> my tree after it is merged.
>
Hi Joerg,
I applied 1st and 2nd patches in my tree.
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
next/cleanup-samsung-iommu
and my -next.
So please go ahead for 3rd patch in your tree. Note that if you need 1st
and 2nd patches for your tree, please merge the
'next/cleanup-samsung-iommu' branch in my tree. If not, will happen
useless conflicts.
If any problems, please let me know.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2012-04-10 19:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 8:32 [PATCH v12 2/3] ARM: EXYNOS: Change System MMU platform device definitions Cho KyongHo
2012-03-15 8:32 ` Cho KyongHo
2012-03-15 8:32 ` Cho KyongHo
2012-03-15 11:12 ` Joerg Roedel
2012-03-15 11:12 ` Joerg Roedel
2012-03-15 11:12 ` Joerg Roedel
2012-03-15 14:39 ` Kukjin Kim
2012-03-15 14:39 ` Kukjin Kim
2012-03-16 9:30 ` Subash Patel
2012-03-16 9:30 ` Subash Patel
2012-03-16 20:47 ` Kukjin Kim
2012-03-16 20:47 ` Kukjin Kim
2012-03-18 13:27 ` Joerg Roedel
2012-03-18 13:27 ` Joerg Roedel
2012-03-18 13:27 ` Joerg Roedel
2012-03-29 1:23 ` Kukjin Kim
2012-03-29 1:23 ` Kukjin Kim
2012-03-29 1:43 ` KyongHo Cho
2012-03-29 1:43 ` KyongHo Cho
2012-03-29 1:43 ` KyongHo Cho
2012-04-10 19:34 ` Kukjin Kim [this message]
2012-04-10 19:34 ` Kukjin Kim
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=4F848B4B.5000308@samsung.com \
--to=kgene.kim@samsung.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--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 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.