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: Tue, 07 Mar 2017 04:01:58 -0800 From: Joe Perches <joe@...ches.com> To: Ingo Molnar <mingo@...nel.org>, Thomas Gleixner <tglx@...utronix.de> Cc: kbuild test robot <fengguang.wu@...el.com>, Rik van Riel <riel@...hat.com>, kbuild-all@...org, LKML <linux-kernel@...r.kernel.org>, tipbuild@...or.com, "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org, Dave Hansen <dave.hansen@...ux.intel.com>, Yu-cheng Yu <yu-cheng.yu@...el.com>, Fenghua Yu <fenghua.yu@...el.com>, Borislav Petkov <bp@...e.de>, Peter Zijlstra <peterz@...radead.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [PATCH] x86/fpu: fix boolreturn.cocci warnings On Tue, 2017-03-07 at 10:01 +0100, Ingo Molnar wrote: > To me a lexical 'true/false' instead of '1/0' is a step backwards in readability > in many cases What cases are those to you? I can't think of any case where 1/0 for true/false is "more readable" for boolean returns to me.
Powered by blists - more mailing lists