motivation behind pr_xxx macros

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



While writing some code on 2.6.32, I have come across some of these
macros that in turn call printk:

pr_emerg
pr_alert
...
pr_debug

Is there any case when should these macros be preferred over explicit
printk statements? What is the motivation behind providing these
macros when this task can already be accomplished by using printk
statements explicitly with priority levels?

Regards,
Himanshu

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux