There are certain client bugs (double unmap, for example) that can cause
the handle->kmap_cnt (an unsigned int) to wrap around from zero. This
causes problems when the handle is destroyed because we have:
while (handle->kmap_cnt)
ion_handle_kmap_put(handle);
which takes a
On Fri, May 23, 2014 at 11:34:59AM -0700, Mitchel Humpherys wrote:
> ++greg-kh and de...@driverdev.osuosl.org
> (my bad for missing you the first time around)
What can I do with this? Please send patches to me in a format that I
can actually apply them in...
thanks,
greg k-h
--
To unsubscribe
++greg-kh and de...@driverdev.osuosl.org
(my bad for missing you the first time around)
On Thu, May 22 2014 at 06:09:11 PM, Colin Cross wrote:
> On Thu, May 22, 2014 at 5:51 PM, Mitchel Humpherys
> wrote:
>> There are certain client bugs (double unmap, for example) that can cause
>> the
++greg-kh and de...@driverdev.osuosl.org
(my bad for missing you the first time around)
On Thu, May 22 2014 at 06:09:11 PM, Colin Cross ccr...@android.com wrote:
On Thu, May 22, 2014 at 5:51 PM, Mitchel Humpherys
mitch...@codeaurora.org wrote:
There are certain client bugs (double unmap, for
On Fri, May 23, 2014 at 11:34:59AM -0700, Mitchel Humpherys wrote:
++greg-kh and de...@driverdev.osuosl.org
(my bad for missing you the first time around)
What can I do with this? Please send patches to me in a format that I
can actually apply them in...
thanks,
greg k-h
--
To unsubscribe
There are certain client bugs (double unmap, for example) that can cause
the handle-kmap_cnt (an unsigned int) to wrap around from zero. This
causes problems when the handle is destroyed because we have:
while (handle-kmap_cnt)
ion_handle_kmap_put(handle);
which takes a
On Thu, May 22, 2014 at 5:51 PM, Mitchel Humpherys
wrote:
> There are certain client bugs (double unmap, for example) that can cause
> the handle->kmap_cnt (an unsigned int) to wrap around from zero. This
> causes problems when the handle is destroyed because we have:
>
> while
There are certain client bugs (double unmap, for example) that can cause
the handle->kmap_cnt (an unsigned int) to wrap around from zero. This
causes problems when the handle is destroyed because we have:
while (handle->kmap_cnt)
ion_handle_kmap_put(handle);
which takes a
There are certain client bugs (double unmap, for example) that can cause
the handle-kmap_cnt (an unsigned int) to wrap around from zero. This
causes problems when the handle is destroyed because we have:
while (handle-kmap_cnt)
ion_handle_kmap_put(handle);
which takes a
On Thu, May 22, 2014 at 5:51 PM, Mitchel Humpherys
mitch...@codeaurora.org wrote:
There are certain client bugs (double unmap, for example) that can cause
the handle-kmap_cnt (an unsigned int) to wrap around from zero. This
causes problems when the handle is destroyed because we have:
10 matches
Mail list logo