diff options
Diffstat (limited to 'target/linux/brcm2708/patches-4.4/0198-drm-vc4-Drop-error-message-on-seqno-wait-timeouts.patch')
-rw-r--r-- | target/linux/brcm2708/patches-4.4/0198-drm-vc4-Drop-error-message-on-seqno-wait-timeouts.patch | 27 |
1 files changed, 0 insertions, 27 deletions
diff --git a/target/linux/brcm2708/patches-4.4/0198-drm-vc4-Drop-error-message-on-seqno-wait-timeouts.patch b/target/linux/brcm2708/patches-4.4/0198-drm-vc4-Drop-error-message-on-seqno-wait-timeouts.patch deleted file mode 100644 index 63a49cee0c..0000000000 --- a/target/linux/brcm2708/patches-4.4/0198-drm-vc4-Drop-error-message-on-seqno-wait-timeouts.patch +++ /dev/null @@ -1,27 +0,0 @@ -From e533472c91247507f73c4120a441d7844eee637a Mon Sep 17 00:00:00 2001 -From: Eric Anholt <eric@anholt.net> -Date: Mon, 25 Jan 2016 14:33:50 -0800 -Subject: [PATCH] drm/vc4: Drop error message on seqno wait timeouts. - -These ioctls end up getting exposed to userspace, and having normal -user requests print DRM errors is obviously wrong. The message was -originally to give us some idea of what happened when a hang occurred, -but we have a DRM_INFO from reset for that. - -Signed-off-by: Eric Anholt <eric@anholt.net> ---- - drivers/gpu/drm/vc4/vc4_gem.c | 3 --- - 1 file changed, 3 deletions(-) - ---- a/drivers/gpu/drm/vc4/vc4_gem.c -+++ b/drivers/gpu/drm/vc4/vc4_gem.c -@@ -352,9 +352,6 @@ vc4_wait_for_seqno(struct drm_device *de - finish_wait(&vc4->job_wait_queue, &wait); - trace_vc4_wait_for_seqno_end(dev, seqno); - -- if (ret && ret != -ERESTARTSYS) -- DRM_ERROR("timeout waiting for render thread idle\n"); -- - return ret; - } - |