On 12/14/12 7:50 PM, Daniel Vetter wrote:
> Dude, you're seriously overshooting here. This patch isn't required
> _at_ _all_ to do cross device sharing/reservations/whatever. We've
> simply discussed TTM documentation in the context of Maartens work,
> and I've suggested to include all the TTM kern
On 12/14/12 7:50 PM, Daniel Vetter wrote:
Dude, you're seriously overshooting here. This patch isn't required
_at_ _all_ to do cross device sharing/reservations/whatever. We've
simply discussed TTM documentation in the context of Maartens work,
and I've suggested to include all the TTM kerneldoc
Dude, you're seriously overshooting here. This patch isn't required
_at_ _all_ to do cross device sharing/reservations/whatever. We've
simply discussed TTM documentation in the context of Maartens work,
and I've suggested to include all the TTM kerneldoc into a nice
DocBook. That way the kerneldoc
Nack,
I'm not against moving the TTM lock away,
when a replacement strategy for the main use case is presented.
but using wording like "unholy", "scares" just because there is a lack
of understanding or because it gets in the way of implementing
cross-device reservation is a really really bad i
Dude, you're seriously overshooting here. This patch isn't required
_at_ _all_ to do cross device sharing/reservations/whatever. We've
simply discussed TTM documentation in the context of Maartens work,
and I've suggested to include all the TTM kerneldoc into a nice
DocBook. That way the kerneldoc
Nack,
I'm not against moving the TTM lock away,
when a replacement strategy for the main use case is presented.
but using wording like "unholy", "scares" just because there is a lack
of understanding or because it gets in the way of implementing
cross-device reservation is a really really bad
... it's the only user. Also move the header fil there.
but seriously, ttm_lock is best left undocumented since
nobody should use that unholy thing..
agreed ;-)
imo we should shovel that under drm/vmwgfx ...
amen
that thing scares me
out of sight, out of mind ...
Signed-off-by: Daniel Vette
... it's the only user. Also move the header fil there.
but seriously, ttm_lock is best left undocumented since
nobody should use that unholy thing..
agreed ;-)
imo we should shovel that under drm/vmwgfx ...
amen
that thing scares me
out of sight, out of mind ...
Signed-off-by: Daniel Vette
