Staging: sm7xx: printk loglevels modified to match the scenario KERN_ERR should be used in place of KERN_INFO in the case of error scenarios. Signed-off-by: anish kumar <anish198519851985@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
diff --git a/drivers/staging/sm7xx/smtcfb.c b/drivers/staging/sm7xx/smtcfb.c index c41d2f7..a164fc4 100644 --- a/drivers/staging/sm7xx/smtcfb.c +++ b/drivers/staging/sm7xx/smtcfb.c
@@ -783,7 +783,7 @@ sfb->fb.screen_base = smtc_VRAMBaseAddress; if (!sfb->fb.screen_base) { - printk(KERN_INFO "%s: unable to map screen memory\n", + printk(KERN_ERR "%s: unable to map screen memory\n", sfb->fb.fix.id); return -ENOMEM; } @@ -938,7 +938,7 @@ } #endif if (!smtc_RegBaseAddress) { - printk(KERN_INFO + printk(KERN_ERR "%s: unable to map memory mapped IO\n", sfb->fb.fix.id); err = -ENOMEM; @@ -973,7 +973,7 @@ smtc_seqw(0x6b, 0x02); break; default: - printk(KERN_INFO + printk(KERN_ERR "No valid Silicon Motion display chip was detected!\n"); goto failed_fb; @@ -1006,7 +1006,7 @@ return 0; failed: - printk(KERN_INFO "Silicon Motion, Inc. primary display init fail\n"); + printk(KERN_ERR "Silicon Motion, Inc. primary display init fail\n"); smtc_unmap_smem(sfb); smtc_unmap_mmio(sfb);