[PATCH 04/23] drm/sman: rip out owner tracking

> In contrast to kms drivers, sis/via _always_ associated a buffer with > a drm fd. So by the time we reach lastclose, all open drm fds are gone > and with them their associated objects. > > So when sis/via call drm_sman_cleanup in their lastclose funcs, that > will free 0 objects. > > The owner

Re: [PATCH 04/23] drm/sman: rip out owner tracking

> In contrast to kms drivers, sis/via _always_ associated a buffer with > a drm fd. So by the time we reach lastclose, all open drm fds are gone > and with them their associated objects. > > So when sis/via call drm_sman_cleanup in their lastclose funcs, that > will free 0 objects. > > The owner

[PATCH 04/23] drm/sman: rip out owner tracking

In contrast to kms drivers, sis/via _always_ associated a buffer with a drm fd. So by the time we reach lastclose, all open drm fds are gone and with them their associated objects. So when sis/via call drm_sman_cleanup in their lastclose funcs, that will free 0 objects. The owner tracking now ser

[PATCH 04/23] drm/sman: rip out owner tracking

In contrast to kms drivers, sis/via _always_ associated a buffer with a drm fd. So by the time we reach lastclose, all open drm fds are gone and with them their associated objects. So when sis/via call drm_sman_cleanup in their lastclose funcs, that will free 0 objects. The owner tracking now ser