Re: [PATCH v2 2/2] drm: kill ->gem_init_object() and friends

2013-10-09 Thread Dave Airlie
>> All drivers embed gem-objects into their own buffer objects. There is no >> reason to keep drm_gem_object_alloc(), gem->driver_private and >> ->gem_init_object() anymore. >> >> New drivers are highly encouraged to do the same. There is no benefit in >> allocating gem-objects separately. Merged

Re: [PATCH v2 2/2] drm: kill ->gem_init_object() and friends

2013-10-02 Thread Alex Deucher
On Wed, Oct 2, 2013 at 4:15 AM, David Herrmann wrote: > All drivers embed gem-objects into their own buffer objects. There is no > reason to keep drm_gem_object_alloc(), gem->driver_private and > ->gem_init_object() anymore. > > New drivers are highly encouraged to do the same. There is no benefit

[PATCH v2 2/2] drm: kill ->gem_init_object() and friends

2013-10-02 Thread David Herrmann
All drivers embed gem-objects into their own buffer objects. There is no reason to keep drm_gem_object_alloc(), gem->driver_private and ->gem_init_object() anymore. New drivers are highly encouraged to do the same. There is no benefit in allocating gem-objects separately. Cc: Dave Airlie Cc: Ale