From: Mark yao <mark.yao@rock-chips.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: David Airlie <airlied@linux.ie>, Heiko Stuebner <heiko@sntech.de>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] drm/rockchip: switch to drm_mm for support arm64 iommu
Date: Wed, 8 Feb 2017 09:15:35 +0800 [thread overview]
Message-ID: <589A7137.4040704@rock-chips.com> (raw)
In-Reply-To: <20170207123859.GD18315@ulmo.ba.sec>
On 2017年02月07日 20:38, Thierry Reding wrote:
> On Tue, Feb 07, 2017 at 04:35:35PM +0800, Mark Yao wrote:
>> Some iommu patches on the series[0] "iommu/rockchip: Fix bugs and
>> enable on ARM64" already landed, So drm/rockchip related patches [1] and [2]
>> ready to landed, this series just rebase them to lastest drm-next.
>>
>> And fix some bugs for drm/rockchip drm_mm
>>
>> [0]: http://www.spinics.net/lists/arm-kernel/msg513781.html
>> [1]: https://patchwork.kernel.org/patch/9196367
>> [2]: https://patchwork.kernel.org/patch/9196369
>>
>> Changes in v2:
>> Advices by Tomasz:
>> add some fixes patches from chromeos project.
> I think those fixes should've been squashed into the patches that they
> fix. It's very unusual to merge patches upstream that are know to have
> been fixed already.
>
> Thierry
Got it, I will fix them at v3 version.
Thanks for review.
--
Ｍark Yao
next prev parent reply other threads:[~2017-02-08 1:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 8:35 [PATCH v2 0/7] drm/rockchip: switch to drm_mm for support arm64 iommu Mark Yao
2017-02-07 8:35 ` [PATCH v2 1/7] drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain Mark Yao
2017-02-07 8:35 ` [PATCH v2 2/7] drm/rockchip: Use common IOMMU API to attach devices Mark Yao
2017-02-07 8:35 ` [PATCH v2 3/7] drm/rockchip: gem: add mutex lock for drm mm Mark Yao
2017-02-07 12:19 ` Thierry Reding
2017-02-08 0:28 ` Mark yao
2017-02-07 8:35 ` [PATCH v2 4/7] drm/rockchip: gem: fixup iommu_map_sg error path Mark Yao
2017-02-07 8:39 ` [PATCH v2 6/7] drm/rockchip: Respect page offset in IOMMU mmap Mark Yao
2017-02-07 12:33 ` Thierry Reding
2017-02-07 8:39 ` [PATCH v2 7/7] drm/rockchip: Call drm_gem_object_release() to destroy GEM base Mark Yao
2017-02-07 12:37 ` Thierry Reding
2017-02-07 13:05 ` Tomasz Figa
2017-02-07 12:38 ` [PATCH v2 0/7] drm/rockchip: switch to drm_mm for support arm64 iommu Thierry Reding
2017-02-08 1:15 ` Mark yao [this message]
2017-02-08 23:36 ` Heiko Stübner
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=589A7137.4040704@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox