> On Apr 4, 2019, at 6:39 PM, Dave Airlie wrote:
>
>> On Fri, 5 Apr 2019 at 08:43, Rodrigo Vivi wrote:
>>
>>> On Thu, Apr 04, 2019 at 03:25:38PM -0700, Rodrigo Vivi wrote:
>>> From: Rodrigo Vivi
>>
>> And it seems that I don't know how to spell my own name anymore! :)
>>
>> If you decide f
Thanks, I'm OK with this patch.
Regards,
Qiang
On Fri, Apr 5, 2019 at 9:39 AM Dave Airlie wrote:
>
> On Fri, 5 Apr 2019 at 08:43, Rodrigo Vivi wrote:
> >
> > On Thu, Apr 04, 2019 at 03:25:38PM -0700, Rodrigo Vivi wrote:
> > > From: Rodrigo Vivi
> >
> > And it seems that I don't know how to spe
On Fri, 5 Apr 2019 at 08:43, Rodrigo Vivi wrote:
>
> On Thu, Apr 04, 2019 at 03:25:38PM -0700, Rodrigo Vivi wrote:
> > From: Rodrigo Vivi
>
> And it seems that I don't know how to spell my own name anymore! :)
>
> If you decide for this patch please let me know, so we can fix while
> pushing to d
On Thu, Apr 04, 2019 at 03:25:38PM -0700, Rodrigo Vivi wrote:
> From: Rodrigo Vivi
And it seems that I don't know how to spell my own name anymore! :)
If you decide for this patch please let me know, so we can fix while
pushing to drm-misc-fixes or tell me to send a v2.
>
> I'm not entirely su
From: Rodrigo Vivi
I'm not entirely sure about the limits we should use
here on ARM based driver, but apparently the entry and limit
are inverted and UINT_MAX cannot be used directly there.
So let's at least for now fix this compilation issue
on a compilation only driver:
CC [M] drivers/gpu/dr
