linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: joro@8bytes.org ('Joerg Roedel')
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 00/12] iommu/exynos: Fixes and Enhancements of System MMU driver with DT
Date: Thu, 10 Jan 2013 20:12:08 +0100	[thread overview]
Message-ID: <20130110191207.GI25591@8bytes.org> (raw)
In-Reply-To: <027601cdef61$2df576a0$89e063e0$@samsung.com>

On Thu, Jan 10, 2013 at 10:34:48AM -0800, Kukjin Kim wrote:
> 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?

Sounds good. Should I take the patch directly from this post? I would
add your Acked-by then and make it the base for the arm/exynos branch.
Once the branch is set-up, as usual it will not be rebased.


	Joerg

  reply	other threads:[~2013-01-10 19:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26  1:53 [PATCH v6 00/12] iommu/exynos: Fixes and Enhancements of System MMU driver with DT 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
2013-01-10 19:12       ` 'Joerg Roedel' [this message]
2013-01-10 19:33         ` Kukjin Kim
2013-01-11 15:52           ` 'Joerg Roedel'
2013-01-03 23:18 ` Sylwester Nawrocki
2013-01-07 10:45   ` KyongHo Cho
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=20130110191207.GI25591@8bytes.org \
    --to=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).