| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 15 Mar 2011 16:11:52 -0700 From: Randy Dunlap <rdunlap@...otime.net> To: lkml <linux-kernel@...r.kernel.org> Cc: torvalds <torvalds@...ux-foundation.org>, Roland Kammerer <dev.rck@...il.com> Subject: [PATCH 3/6] Documentation: update header filename in CodingStyle From: Roland Kammerer <dev.rck@...il.com> pr_info() and pr_debug() are in linux/printk.h, not linux/kernel.h. Last updated is unnecessary, we have git for that. Signed-off-by: Roland Kammerer <dev.rck@...il.com> Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com> --- Documentation/CodingStyle | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) --- lnx-2638-rc8.orig/Documentation/CodingStyle +++ lnx-2638-rc8/Documentation/CodingStyle @@ -659,7 +659,7 @@ There are a number of driver model diagn which you should use to make sure messages are matched to the right device and driver, and are tagged with the right level: dev_err(), dev_warn(), dev_info(), and so forth. For messages that aren't associated with a -particular device, <linux/kernel.h> defines pr_debug() and pr_info(). +particular device, <linux/printk.h> defines pr_debug() and pr_info(). Coming up with good debugging messages can be quite a challenge; and once you have them, they can be a huge help for remote troubleshooting. Such @@ -819,6 +819,3 @@ language C, URL: http://www.open-std.org Kernel CodingStyle, by greg@...ah.com at OLS 2002: http://www.kroah.com/linux/talks/ols_2002_kernel_codingstyle_talk/html/ --- -Last updated on 2007-July-13. - -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists