On Thursday, 2018-10-18 08:02:42 -0500, Jason Ekstrand wrote:
> On October 18, 2018 05:40:14 Eric Engestrom wrote:
>
> > On Wednesday, 2018-10-17 15:14:03 -0500, Jason Ekstrand wrote:
> > > We already have wsi_device and we know the instance allocator at
> > > wsi_device_init time so there's no n
On October 18, 2018 05:40:14 Eric Engestrom wrote:
On Wednesday, 2018-10-17 15:14:03 -0500, Jason Ekstrand wrote:
We already have wsi_device and we know the instance allocator at
wsi_device_init time so there's no need to pass it into the physical
device queries. This also fixes a memory allo
Reviewed-by: Lionel Landwerlin
On 17/10/2018 21:14, Jason Ekstrand wrote:
We already have wsi_device and we know the instance allocator at
wsi_device_init time so there's no need to pass it into the physical
device queries. This also fixes a memory allocation domain bug that can
occur if Creat
On Wednesday, 2018-10-17 15:14:03 -0500, Jason Ekstrand wrote:
> We already have wsi_device and we know the instance allocator at
> wsi_device_init time so there's no need to pass it into the physical
> device queries. This also fixes a memory allocation domain bug that can
> occur if CreateSwapch
We already have wsi_device and we know the instance allocator at
wsi_device_init time so there's no need to pass it into the physical
device queries. This also fixes a memory allocation domain bug that can
occur if CreateSwapchain gets called prior to any queries (not likely)
in which case the cac