linux-kernel - Re: [PATCH 1/4] posix-timers: Refactoring of CPUCLOCK* 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1279564962.21763.8.camel@c-dwalke-linux.qualcomm.com>
Date:	Mon, 19 Jul 2010 11:42:42 -0700
From:	Daniel Walker <dwalker@...eaurora.org>
To:	Tomasz Buchert <tomasz.buchert@...ia.fr>
Cc:	linux-kernel@...r.kernel.org,
	Stanislaw Gruszka <sgruszka@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 1/4] posix-timers: Refactoring of CPUCLOCK* macros

On Mon, 2010-07-19 at 13:34 +0200, Tomasz Buchert wrote:
> This is merely a preparation to introduce wall time
> clocks for threads/processes. All occurences of
> CPUCLOCK* macros were replaced by CLOCK*.

It seems like it would be better to make this naming more specific that
less. Couldn't you say "POSIX_CLOCK" or something like that?

Daniel
-- 
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

--
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/