From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: "Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH V3 1/4] ARM64: dts: rockchip: rk3328 add iommu nodes
Date: Thu, 27 Jul 2017 14:15:18 +0200 [thread overview]
Message-ID: <20170727121518.GB21502@8bytes.org> (raw)
In-Reply-To: <1668393.AqADimcrsl@diego>
Hey Heiko,
On Wed, Jul 26, 2017 at 03:53:06PM +0200, Heiko Stübner wrote:
> Having code and dts changes go through different trees is no problem, as they
> don't have a compile-time dependencies on each other and come together nicely
> in linux-next again.
Okay, I removed
ARM64: dts: rockchip: rk3328 add iommu nodes
ARM: dts: rockchip: rk322x add iommu nodes
ARM64: dts: rockchip: rk3368 add iommu nodes
ARM64: dts: rockchip: rk3399 add iommu nodes
ARM64: dts: rockchip: rk3328 add iommu nodes
ARM: dts: rockchip: rk322x add iommu nodes
ARM64: dts: rockchip: rk3368 add iommu nodes
ARM64: dts: rockchip: rk3399 add iommu nodes
from my tree again and kept
Docs: dt: rockchip: add rockchip,disable-mmu-reset property
iommu/rockchip: add multi irqs support
iommu/rockchip: ignore isp mmu reset operation
Regards,
Joerg
next prev parent reply other threads:[~2017-07-27 12:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 2:32 [PATCH V3 1/4] ARM64: dts: rockchip: rk3328 add iommu nodes Simon Xue
[not found] ` <1500863530-32792-1-git-send-email-xxm-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-07-24 2:32 ` [PATCH V3 2/4] ARM: dts: rockchip: rk322x " Simon Xue
[not found] ` <1500863530-32792-2-git-send-email-xxm-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-21 21:17 ` Heiko Stuebner
2017-07-24 2:32 ` [PATCH V3 3/4] ARM64: dts: rockchip: rk3368 " Simon Xue
[not found] ` <1500863530-32792-3-git-send-email-xxm-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-21 21:08 ` Heiko Stuebner
2017-07-24 2:32 ` [PATCH V3 4/4] ARM64: dts: rockchip: rk3399 " Simon Xue
[not found] ` <1500863530-32792-4-git-send-email-xxm-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-21 21:14 ` Heiko Stuebner
2017-07-26 10:58 ` [PATCH V3 1/4] ARM64: dts: rockchip: rk3328 " Joerg Roedel
[not found] ` <20170726105818.GK15833-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-07-26 11:44 ` Heiko Stübner
2017-07-26 12:27 ` Joerg Roedel
[not found] ` <20170726122753.GQ15833-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-07-26 13:53 ` Heiko Stübner
2017-07-27 12:15 ` Joerg Roedel [this message]
[not found] ` <20170727121518.GB21502-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-07-27 12:26 ` Heiko Stübner
2017-07-27 12:45 ` Joerg Roedel
2017-08-21 21:08 ` Heiko Stuebner
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=20170727121518.GB21502@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).