From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 5/5] ARM: dts: mt2701: add iommu/smi dtsi node for mt2701
Date: Wed, 22 Jun 2016 10:58:29 +0200 [thread overview]
Message-ID: <20160622085829.GH11432@8bytes.org> (raw)
In-Reply-To: <1466584741.8787.22.camel@mtksdaap41>
On Wed, Jun 22, 2016 at 04:39:01PM +0800, Honghui Zhang wrote:
> I think that driver and dtsi could merged separately, I would prefer
> those previous patches stay in the tree if it's OK for you.
Sure, I send them upstream through my tree.
Thanks,
Joerg
next prev parent reply other threads:[~2016-06-22 8:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 9:50 [PATCH v4 0/5] MT2701 iommu support honghui.zhang at mediatek.com
2016-06-08 9:50 ` [PATCH v4 1/5] dt-bindings: mediatek: add descriptions for mediatek mt2701 iommu and smi honghui.zhang at mediatek.com
2016-06-08 9:50 ` [PATCH v4 2/5] iommu/mediatek: move the common struct into header file honghui.zhang at mediatek.com
2016-06-08 9:50 ` [PATCH v4 3/5] memory/mediatek: add support for mt2701 honghui.zhang at mediatek.com
2016-06-08 9:51 ` [PATCH v4 4/5] iommu/mediatek: add support for mtk iommu generation one HW honghui.zhang at mediatek.com
2016-06-08 9:51 ` [PATCH v4 5/5] ARM: dts: mt2701: add iommu/smi dtsi node for mt2701 honghui.zhang at mediatek.com
2016-06-21 9:41 ` Joerg Roedel
2016-06-21 9:55 ` Honghui Zhang
2016-06-21 9:57 ` Joerg Roedel
2016-06-22 5:45 ` Eddie Huang
2016-06-22 7:45 ` Honghui Zhang
2016-06-22 8:31 ` Joerg Roedel
2016-06-22 8:39 ` Honghui Zhang
2016-06-22 8:58 ` Joerg Roedel [this message]
2016-07-03 6:24 ` Matthias Brugger
2016-07-03 19:12 ` Matthias Brugger
2016-07-04 1:32 ` Honghui Zhang
2016-07-04 8:00 ` Matthias Brugger
2017-01-13 14:54 ` Matthias Brugger
2017-01-16 2:48 ` Honghui Zhang
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=20160622085829.GH11432@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).