drm: remove some potentially dangerous DRM_ERRORs
authorJesse Barnes <jbarnes@virtuousgeek.org>
Mon, 7 Nov 2011 20:03:23 +0000 (12:03 -0800)
committerBen Hutchings <ben@decadent.org.uk>
Wed, 19 Sep 2012 14:04:33 +0000 (15:04 +0100)
commit770ba2389ee98d51fe12d738e0ed4006caefca47
treec795b14f9977b929dc1c80f6a1fe20dad8711b68
parentc09ccfb99f423aa9cdd865c72695c72402f2eb97
drm: remove some potentially dangerous DRM_ERRORs

commit acb4b992d8a13728044f430b47b9199aa45993e9 upstream.

Each of these error messages can be caused by a broken or malicious
userspace wanting to spam the dmesg with useless info.  They're really
not worthy of DRM_DEBUG statements either; those are generally only
useful during bringup of new hardware or versions, and ought to be
removed before going upstream anyway.

Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Reviewed-by: Alex Deucher <alexdeucher@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
[bwh: Backported to 3.2: s/r\./r->/ in drm_mode_addfb()]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
drivers/gpu/drm/drm_crtc.c