Am Donnerstag, den 29.11.2012, 11:38 -0700 schrieb Stephen Warren:

On 11/29/2012 04:47 AM, Thierry Reding wrote:

quoted

I agree. But I also fear that there will be changes eventually and 
having both go in via different tree requires those trees to be
merged in a specific order to avoid breakage should the API change.
This will be particularly ugly in linux-next.

That's why I explicitly proposed to take this into
drivers/gpu/drm/tegra for the time being, until we can be
reasonably sure that the API is fixed. Then I'm fine with moving it
wherever seems the best fit. Even then there might be the
occasional dependency, but they should get fewer and fewer as the
code matures.

It is acceptable for one maintainer to ack patches, and another
maintainer to merge a series that touches both "their own" code and
code owned by another tree. This should of course only be needed when
inter-module APIs change; changes to code within a module shouldn't
require this.

I'm with Thierry here. I think there is a fair chance that we won't get
the API right from the start, even when trying to come up with something
that sounds sane to everyone. It's also not desirable to delay gr2d
going into mainline until we are all completely satisfied with the API.

I also fail to see how host1x module being in the DRM directory hinders
any downstream development. So I'm in favour of keeping host1x besides
the other DRM components to lower the burden for API changes and move it
out into some more generic directory, once we feel confident that the
API is reasonable stable.

Regards,
Lucas