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: Mon, 31 May 2010 00:19:47 -0700 (PDT) From: David Miller <davem@...emloft.net> To: fthain@...egraphics.com.au Cc: joe@...ches.com, p_gortmaker@...oo.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, linux-m68k@...r.kernel.org Subject: Re: [PATCH] mac8390: change an error return code and some cleanup, take 4 From: Finn Thain <fthain@...egraphics.com.au> Date: Sat, 29 May 2010 03:29:01 +1000 (EST) > @@ -662,7 +665,7 @@ static void mac8390_no_reset(struct net_ > { > ei_status.txing = 0; > if (ei_debug > 1) > - pr_info("reset not supported\n"); > + printk(KERN_DEBUG pr_fmt("reset not supported\n")); > return; Use pr_debug() or pr_devel(). Anything which explicitly codes out a "printk(KERN_*" is suspect, we have interfaces for this. The whole point of defining pr_fmt at the top of the driver is so that in the driver, we use pr_foo() which includes the pr_fmt string at the beginning. If you bypass it you avoid the intended effect of that pr_fmt define. This is getting tiring Finn. So we're already past 4 iterations of this silly simple patch, and I want to remind you yet again what an incredibly hard time you gave Joe Perches for his changes to this file which in the end were entirely correct and well formed, and he got it right on his first attempt. I advise you to think twice before snapping at another developer's work in the future. -- 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