X-Git-Url: https://git.karo-electronics.de/?a=blobdiff_plain;f=Documentation%2FCodingStyle;h=1cd3478e5834e0a7a8e1110ebd1a736989794148;hb=f74b9444192c60603020c61d7915b72893137edc;hp=8bb37237ebd25b19759cc47874c63155406ea28f;hpb=5e75c5f5d723074b1ceefe916c3005888e431d12;p=karo-tx-linux.git diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle index 8bb37237ebd2..1cd3478e5834 100644 --- a/Documentation/CodingStyle +++ b/Documentation/CodingStyle @@ -659,7 +659,7 @@ There are a number of driver model diagnostic macros in 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, defines pr_debug() and pr_info(). +particular device, 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/JTC1/SC22/WG14/ Kernel CodingStyle, by greg@kroah.com at OLS 2002: http://www.kroah.com/linux/talks/ols_2002_kernel_codingstyle_talk/html/ --- -Last updated on 2007-July-13. -