| 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: <20070711084549.93bb433e.rdunlap@xenotime.net> Date: Wed, 11 Jul 2007 08:45:49 -0700 From: Randy Dunlap <rdunlap@...otime.net> To: Christoph Hellwig <hch@....de> Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, rusty@...tcorp.com.au, linux-mm@...ck.org Subject: Re: lguest, Re: -mm merge plans for 2.6.23 On Wed, 11 Jul 2007 14:23:24 +0200 Christoph Hellwig wrote: ... > > lguest-the-guest-code.patch > > lguest-the-host-code.patch > > lguest-the-host-code-lguest-vs-clockevents-fix-resume-logic.patch > > lguest-the-asm-offsets.patch > > lguest-the-makefile-and-kconfig.patch > > lguest-the-console-driver.patch > > lguest-the-net-driver.patch > > lguest-the-block-driver.patch > > lguest-the-documentation-example-launcher.patch > > Just started to reading this (again) so no useful comment here, but it > would be nice if the code could follow CodingStyle and place the || and > && at the end of the line in multiline conditionals instead of at the > beginning of the new one. I prefer them at the ends of lines also, but that's not in CodingStyle, it's just how we do it most of the time (so "coding style", without caps). --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** - 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