On 2017?02?27? 04:45, Daniel Vetter wrote: > On Thu, Feb 16, 2017 at 11:02:31AM +0800, Mark yao wrote: >> Hi Dave >> >> After convert to drm_mm, rockchip arm64 platform can works with iommu, like >> rk3399. it's import patches for rockchip arm64 platform >> >> And these patches already have full reviewed, I hope these patches can be >> landed. >> >> Best regards >> >> The following changes since commit 13f62f54d174d3417c3caaafedf5e22a0a03e442: >> >> Merge branch 'drm-next-4.11' of git://people.freedesktop.org/~agd5f/linux >> into drm-next (2017-02-10 10:13:30 +1000) >> >> are available in the git repository at: >> >> >> https://github.com/markyzq/kernel-drm-rockchip.git >> drm-rockchip-next-2017-02-16 >> >> for you to fetch changes up to 1aa5ca6e3ec63aa5815d78646748e88a7ceb1c8e: >> >> drm/rockchip: Use common IOMMU API to attach devices (2017-02-15 08:52:13 >> +0800) >> >> ---------------------------------------------------------------- >> Shunqian Zheng (1): >> drm/rockchip: Use common IOMMU API to attach devices >> >> Tomasz Figa (1): >> drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain > I thought we've moved rockchip into drm-misc ...? Sorry, I'm not clear understand how the drm-misc maintain before, later patches would go through drm-misc > Can you and Sean Paul please talk and figure out how exactly you want to > maintain this driver? Move drm/rockchip into drm-misc is good, Thanks Sean Paul's work. I'm learning how to maintain drm/rockchip with drm-misc. But I'm not understand drm-misc's step, I'm confused that: do I need to pick up patches to drm-misc by myself? or I just give a ACK on patches, and then Sean or other drm-misc's guys will pick patches up to drm-misc? Thanks. > The current situation where we have stuff going in > independently through different maintainers is not great at all. If you > can't get agreement, we'll just make you agree by arbitrarily rolling the > dice or something silly like that :-) > -Daniel -- ?ark Yao
