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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1427792978.10376.5.camel@perches.com>
Date:	Tue, 31 Mar 2015 02:09:38 -0700
From:	Joe Perches <joe@...ches.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH 19/25] sched: Use bool function return values of
 true/false not 1/0

On Tue, 2015-03-31 at 10:53 +0200, Peter Zijlstra wrote:
> On Mon, Mar 30, 2015 at 04:46:17PM -0700, Joe Perches wrote:
> > Use the normal return values for bool fsnctions
> > 
> > Update the other sets of ret in try_wait_for_completion.
> 
> I'm missing a why; why are you doing this?

It's just a trivial little consistency patch to
make bool functions return bool values instead of
1 or 0 (even though of course 1 and 0 are the
values for true and false)

There's something like 13000 uses of return true
or return false in the tree vs these 180 or so
uses of 1 and 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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ