On Tue, Sep 26, 2017 at 10:20:47AM +0200, Daniel Vetter wrote:
> On Tue, Sep 26, 2017 at 12:17:28AM +0530, Aishwarya Pant wrote:
> > The IDR deletion interface now returns the deleted entry or NULL if it was
> > not
> > present. So we don't have to do the extra work of checking if we have a
> >
On Tue, 26 Sep 2017, Daniel Vetter wrote:
> On Tue, Sep 26, 2017 at 10:47 AM, Daniel Vetter wrote:
> > On Tue, Sep 26, 2017 at 10:38 AM, Julia Lawall wrote:
> >>
> >>
> >> On Tue, 26 Sep 2017, Daniel Vetter wrote:
> >>
> >>> On Tue, Sep 26, 2017 at
On Tue, Sep 26, 2017 at 10:47 AM, Daniel Vetter wrote:
> On Tue, Sep 26, 2017 at 10:38 AM, Julia Lawall wrote:
>>
>>
>> On Tue, 26 Sep 2017, Daniel Vetter wrote:
>>
>>> On Tue, Sep 26, 2017 at 12:17:28AM +0530, Aishwarya Pant wrote:
>>> > The IDR deletion
On Tue, Sep 26, 2017 at 10:38 AM, Julia Lawall wrote:
>
>
> On Tue, 26 Sep 2017, Daniel Vetter wrote:
>
>> On Tue, Sep 26, 2017 at 12:17:28AM +0530, Aishwarya Pant wrote:
>> > The IDR deletion interface now returns the deleted entry or NULL if it was
>> > not
>> > present.
On Tue, 26 Sep 2017, Daniel Vetter wrote:
> On Tue, Sep 26, 2017 at 12:17:28AM +0530, Aishwarya Pant wrote:
> > The IDR deletion interface now returns the deleted entry or NULL if it was
> > not
> > present. So we don't have to do the extra work of checking if we have a
> > reference on the
On Tue, Sep 26, 2017 at 12:17:28AM +0530, Aishwarya Pant wrote:
> The IDR deletion interface now returns the deleted entry or NULL if it was not
> present. So we don't have to do the extra work of checking if we have a
> reference on the drm_gem_object, this can be handled by checking the return
>