On 06.10.2016 16:43, Marek Olšák wrote:
On Thu, Oct 6, 2016 at 4:24 PM, Alex Deucher wrote:
On Thu, Oct 6, 2016 at 6:28 AM, Marek Olšák wrote:
Do we need to bump the DRM version for this bug fix?
Alternatively, we could just cc stable. Being that
On Thu, Oct 6, 2016 at 10:43 AM, Marek Olšák wrote:
> On Thu, Oct 6, 2016 at 4:24 PM, Alex Deucher wrote:
>> On Thu, Oct 6, 2016 at 6:28 AM, Marek Olšák wrote:
>>> Do we need to bump the DRM version for this bug fix?
>>>
>>
>>
On Thu, Oct 6, 2016 at 4:24 PM, Alex Deucher wrote:
> On Thu, Oct 6, 2016 at 6:28 AM, Marek Olšák wrote:
>> Do we need to bump the DRM version for this bug fix?
>>
>
> Alternatively, we could just cc stable. Being that the whole reset
> handling is mesa
On Thu, Oct 6, 2016 at 6:28 AM, Marek Olšák wrote:
> Do we need to bump the DRM version for this bug fix?
>
Alternatively, we could just cc stable. Being that the whole reset
handling is mesa is till kind of up in the air, I'm not sure how
critical it is.
Alex
> Marek
>
>
>
Do we need to bump the DRM version for this bug fix?
Marek
On Oct 4, 2016 10:20 AM, "Christian König" wrote:
> Am 04.10.2016 um 09:45 schrieb Nicolai Hähnle:
>
>> From: Nicolai Hähnle
>>
>> Ensure that we really only report a GPU reset if one
Am 04.10.2016 um 09:45 schrieb Nicolai Hähnle:
From: Nicolai Hähnle
Ensure that we really only report a GPU reset if one has happened since the
creation of the context.
Signed-off-by: Nicolai Hähnle
Reviewed-by: Christian König
From: Nicolai Hähnle
Ensure that we really only report a GPU reset if one has happened since the
creation of the context.
Signed-off-by: Nicolai Hähnle
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c | 3 +++
1 file changed, 3 insertions(+)
diff