linux-kernel - Re: [PATCH] include: kernel.h: deduplicate code implementing clamp* macros

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] [day] [month] [year] [list]

Message-ID: <xa1tvboaywqc.fsf@mina86.com>
Date:	Fri, 26 Sep 2014 22:04:27 +0200
From:	Michal Nazarewicz <mina86@...a86.com>
To:	Hagen Paul Pfeifer <hagen@...u.net>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Mark Rustad <mark.d.rustad@...el.com>,
	"Kirsher\, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH] include: kernel.h: deduplicate code implementing clamp* macros

On Thu, Sep 25 2014, Hagen Paul Pfeifer <hagen@...u.net> wrote:
> On 25 September 2014 17:50, Michal Nazarewicz <mina86@...a86.com> wrote:
>
>> - * @min: minimum allowable value
>> - * @max: maximum allowable value
>> + * @lo: minimum allowable value
>> + * @hi: maximum allowable value
>
> Ok, but why do you rename min/max to low/high after so many years?
> min/max is just perfect

To match argument names of the clamp macro (which got renamed when
rewriting min3, max3 and clamp), but I don't really care either way.

-- 
Best regards,                                         _     _
.o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
..o | Computer Science,  Michał “mina86” Nazarewicz    (o o)
ooo +--<mpn@...gle.com>--<xmpp:mina86@...ber.org>--ooO--(_)--Ooo--
--
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/