On Tue, Jan 28, 2020 at 04:58:07PM -0300, Ezequiel Garcia wrote:
> On Wed, 2020-01-22 at 09:04 +0100, Daniel Vetter wrote:
> > On Sat, Dec 14, 2019 at 01:20:49PM -0300, Ezequiel Garcia wrote:
> > > It's not entirely obvious why these messages have
> > > "info" severity. In any case, add a proper dr
On Wed, 2020-01-22 at 09:04 +0100, Daniel Vetter wrote:
> On Sat, Dec 14, 2019 at 01:20:49PM -0300, Ezequiel Garcia wrote:
> > It's not entirely obvious why these messages have
> > "info" severity. In any case, add a proper driver prefix
> > to give the user a bit of context of where they are comin
On Sat, Dec 14, 2019 at 01:20:49PM -0300, Ezequiel Garcia wrote:
> It's not entirely obvious why these messages have
> "info" severity. In any case, add a proper driver prefix
> to give the user a bit of context of where they are coming from.
So the i915 one makes some sense, it's for oom. Which s
On Sat, 2019-12-14 at 13:20 -0300, Ezequiel Garcia wrote:
> It's not entirely obvious why these messages have
> "info" severity. In any case, add a proper driver prefix
> to give the user a bit of context of where they are coming from.
>
> Signed-off-by: Ezequiel Garcia
Gentle ping.
Thanks,
Eze
It's not entirely obvious why these messages have
"info" severity. In any case, add a proper driver prefix
to give the user a bit of context of where they are coming from.
Signed-off-by: Ezequiel Garcia
---
drivers/gpu/drm/i915/gem/i915_gem_shrinker.c | 2 ++
drivers/gpu/drm/msm/msm_gem_shri
