On 8/28/19 10:48, Srinivas Kandagatla wrote:
>
>
> On 28/08/2019 08:50, Jorge Ramirez wrote:
>> On 8/27/19 23:45, Srinivas Kandagatla wrote:
>>> On 23/08/2019 16:23, Jorge Ramirez-Ortiz wrote:
can you add me as a co-author to this patch please?
>>> No problem I can do that if you feel so!
>>
On 28/08/2019 08:50, Jorge Ramirez wrote:
On 8/27/19 23:45, Srinivas Kandagatla wrote:
On 23/08/2019 16:23, Jorge Ramirez-Ortiz wrote:
can you add me as a co-author to this patch please?
No problem I can do that if you feel so!
yes please. thanks!
since I spent about a day doing the anal
On 8/27/19 23:45, Srinivas Kandagatla wrote:
>
> On 23/08/2019 16:23, Jorge Ramirez-Ortiz wrote:
>> can you add me as a co-author to this patch please?
>
> No problem I can do that if you feel so!
yes please. thanks!
>
>> since I spent about a day doing the analysis, sent you a fix that
>> ma
On 23/08/2019 16:23, Jorge Ramirez-Ortiz wrote:
can you add me as a co-author to this patch please?
No problem I can do that if you feel so!
since I spent about a day doing the analysis, sent you a fix that
maintained the API used by the library and explained you how to
reproduce the issu
dma buf refcount has to be done by the driver which is going to use the fd.
This driver already does refcount on the dmabuf fd if its actively using it
but also does an additional refcounting via extra ioctl.
This additional refcount can lead to memory leak in cases where the
applications fail to c
5 matches
Mail list logo
