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: <4C44BF8D.2020002@inria.fr>
Date:	Mon, 19 Jul 2010 23:11:41 +0200
From:	Tomasz Buchert <Tomasz.Buchert@...ia.fr>
To:	Daniel Walker <dwalker@...eaurora.org>
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

Daniel Walker a écrit :
> On Mon, 2010-07-19 at 22:59 +0200, Tomasz Buchert wrote:
>> Daniel Walker a écrit :
>>> 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
>> Hi Daniel.
>> Sure. However, technically, my wall clocks have nothing to do
>> with POSIX. Still the code is inside a file with "posix" prefix,
>> so you are right.
>> I will resend patch series as soon as it is done. Could you
>> elaborate on another patches?
> 
> I wasn't suggesting that adding "POSIX" is the only option, but adding
> something more so it's not just "CLOCK" .
> 
> You mean you want me to review the other patches also ? 
> 
> Daniel
> 
"POSIX" looks good to me.
Reviewing the other patches would be great, because they actually do real stuff.

Tomek


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