linux-kernel - Re: [PATCH 03/16] GFS2: bmap and inode functions

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 2 Sep 2006 20:47:21 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	Steven Whitehouse <swhiteho@...hat.com>,
	linux-kernel@...r.kernel.org,
	Russell Cattelan <cattelan@...hat.com>,
	David Teigland <teigland@...hat.com>, hch@...radead.org
Subject: Re: [PATCH 03/16] GFS2: bmap and inode functions


* Jan Engelhardt <jengelh@...ux01.gwdg.de> wrote:

> 
> >btw., it is in CodingStyle too:
> 
> It may be used in a lot of places, but there is no explicit written 
> rule. That's why there actually *IS* "if(" in the kernel too.

Not all obvious things are written into it, it's not a legal document. 
Currently only 1.2% of the toplevel */*.c files have the 'if(' 
construct. It's just a small style bug (it's not a big issue at all), i 
was only nitpicking. Lets move over to more important issues, ok? :-)

	Ingo

-- 
VGER BF report: H 0
-
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/