| 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: Fri, 25 Dec 2009 14:26:42 +0100 From: Pavel Machek <pavel@....cz> To: mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org, joe@...ches.com, torvalds@...ux-foundation.org, peterz@...radead.org, efault@....de, akpm@...ux-foundation.org, tglx@...utronix.de, mingo@...e.hu Cc: linux-tip-commits@...r.kernel.org Subject: Re: [tip:sched/urgent] sched: Restore printk sanity On Sun 2009-12-20 18:00:38, tip-bot for Peter Zijlstra wrote: > Commit-ID: 6c9a74afc5d95321e33a727b3c563f3e7d6c4a5c > Gitweb: http://git.kernel.org/tip/6c9a74afc5d95321e33a727b3c563f3e7d6c4a5c > Author: Peter Zijlstra <peterz@...radead.org> > AuthorDate: Sun, 20 Dec 2009 14:23:57 +0100 > Committer: Ingo Molnar <mingo@...e.hu> > CommitDate: Sun, 20 Dec 2009 18:45:57 +0100 > > sched: Restore printk sanity > > Revert the braindead pr_* crap. (Commit 663997d "sched: Use > pr_fmt() and pr_<level>()") > > It's dumb and causes stupid "sched: " strings all over the place. It seems rest of kernel is moving towards pr_*. just removing the "sched:" would be better for consistency. Or alternatively... deprecate pr_*? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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