On 25/01/2018 11:32, Jani Nikula wrote:
On Wed, 24 Jan 2018, Tvrtko Ursulin wrote:
On 24/01/2018 16:23, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2018-01-24 16:18:15)
From: Tvrtko Ursulin
This series tries to solve a few issues in the current DRM logging code to
primarily make it clearer
On Wed, 24 Jan 2018, Tvrtko Ursulin wrote:
> On 24/01/2018 16:23, Chris Wilson wrote:
>> Quoting Tvrtko Ursulin (2018-01-24 16:18:15)
>>> From: Tvrtko Ursulin
>>>
>>> This series tries to solve a few issues in the current DRM logging code to
>>> primarily make it clearer which messages belong to
On 24/01/2018 16:23, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2018-01-24 16:18:15)
From: Tvrtko Ursulin
This series tries to solve a few issues in the current DRM logging code to
primarily make it clearer which messages belong to which driver.
Main problem is that currently some logging f
Quoting Tvrtko Ursulin (2018-01-24 16:18:15)
> From: Tvrtko Ursulin
>
> This series tries to solve a few issues in the current DRM logging code to
> primarily make it clearer which messages belong to which driver.
>
> Main problem is that currently some logging functions allow individual drivers
From: Tvrtko Ursulin
This series tries to solve a few issues in the current DRM logging code to
primarily make it clearer which messages belong to which driver.
Main problem is that currently some logging functions allow individual drivers
to override the log prefix (since they are defined as ma
