| 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
| ||
|
Message-ID: <1350607397.22385.11.camel@joe-AO722> Date: Thu, 18 Oct 2012 17:43:17 -0700 From: Joe Perches <joe@...ches.com> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Kay Sievers <kay@...y.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 00/23] printk: refactoring On Thu, 2012-10-18 at 16:16 -0700, Andrew Morton wrote: > On Tue, 16 Oct 2012 23:06:04 -0700 > Joe Perches <joe@...ches.com> wrote: > > > Make printk a bit more readable. [] > OK, nobody's allowed to change the printk code for two months. [filelist] > It wouldn't hurt to describe the design here a bit. How was the code > partitioned and what is the role of each file? Design? Have you looked at printk recently? I think you called it something like "eye gouging" or maybe "burn it down". Dunno how anyone could consider what there anything other than accreted. I just tried to break it up into somewhat sensible blocks. > That's reasonably obvious from the names, but some might wonder about > the difference between printk_log and printk_syslog and how that > division was decided upon. None of the filenames are great. I still want to break out the console code from what's left of printk.c eventually. I think what would help most is a Documentation/printk.txt file explaining how it all works. cheers, Joe -- 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