Gerd Hoffmann
2019-Feb-01 08:10 UTC
[PATCH v2 2/6] drm/virtio: use struct to pass params to virtio_gpu_object_create()
> > - ret = virtio_gpu_gem_create(file_priv, dev, args->size, &gobj, > > + params.pinned = false, > > You have a comma here, but assigning to false isn't really necessary > since the struct is zeroed. Same goes for the same assignment further down.Hmm, yes, but it likewise isn't used, so I think I can just scratch it altogether. It's also wrong, virtio-gpu objects don't move around, so they are all pinned. Not that this bug changes much in practice given virtio-gpu supports a single kind of storage only, so there is no opportunity for ttm to try move objects from one to another. I'll fix it nevertheless in v3. cheers, Gerd
Apparently Analagous Threads
- [PATCH 05/10] drm/virtio: use struct to pass params to virtio_gpu_object_create()
- [PATCH v3 2/5] drm/virtio: use struct to pass params to virtio_gpu_object_create()
- [PATCH 09/10] drm/virtio: move virtio_gpu_cmd_create_resource call into virtio_gpu_object_create
- [PATCH 06/10] drm/virtio: params struct for virtio_gpu_cmd_create_resource()
- [PATCH v3 3/5] drm/virtio: params struct for virtio_gpu_cmd_create_resource()