[PATCH trivial] drm: log level in print_hex_dump_bytes is redundant

From: Kyle McMartin
Date: Tue Aug 31 2010 - 22:13:10 EST


Ends up with a dmesg like:
[drm:drm_edid_block_valid] *ERROR* Raw EDID:
<3>00 ff ff ff ff ff ff 00 10 ac 29 a0 53 48 4e 31 ..........).SHN1
<3>14 12 01 03 0e 34 20 7f ff ff ff ff ff ff ff ff .....4 .........

Since print_hex_dump_bytes implicitly adds KERN_DEBUG.

Would probably be nice to pretty print the encoder that found the bad
EDID, but it seems in some cases another caller of drm_edid_is_valid
will do that, so probably unnecessary...

Signed-off-by: Kyle McMartin <kyle@xxxxxxxxxx>
---
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 96e9631..32a167c 100644
--- a/drivers/gpu/drm/drm_edid.c
+++ b/drivers/gpu/drm/drm_edid.c
@@ -186,7 +186,7 @@ drm_edid_block_valid(u8 *raw_edid)
bad:
if (raw_edid) {
DRM_ERROR("Raw EDID:\n");
- print_hex_dump_bytes(KERN_ERR, DUMP_PREFIX_NONE, raw_edid, EDID_LENGTH);
+ print_hex_dump_bytes("", DUMP_PREFIX_NONE, raw_edid, EDID_LENGTH);
printk("\n");
}
return 0;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/