From: Tomasz Buchert <Tomasz.Buchert@inria.fr>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: linux-kernel@vger.kernel.org,
Stanislaw Gruszka <sgruszka@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 1/4] posix-timers: Refactoring of CPUCLOCK* macros
Date: Mon, 19 Jul 2010 22:59:10 +0200 [thread overview]
Message-ID: <4C44BC9E.30202@inria.fr> (raw)
In-Reply-To: <1279564962.21763.8.camel@c-dwalke-linux.qualcomm.com>
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?
Tomek
next prev parent reply other threads:[~2010-07-19 20:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 11:34 [PATCH 0/4] Wall time clocks + change in access rules Tomasz Buchert
2010-07-19 11:34 ` [PATCH 1/4] posix-timers: Refactoring of CPUCLOCK* macros Tomasz Buchert
2010-07-19 11:34 ` [PATCH 2/4] posix-cpu-timers: Introduction of wall clocks Tomasz Buchert
2010-07-19 11:34 ` [PATCH 3/4] posix-cpu-timers: Wider access to the thread clocks Tomasz Buchert
2010-07-19 11:34 ` [PATCH 4/4] posix-cpu-timers: posix-cpu-timers.c renamed to posix-task-timers.c Tomasz Buchert
2010-07-19 18:42 ` [PATCH 1/4] posix-timers: Refactoring of CPUCLOCK* macros Daniel Walker
2010-07-19 20:59 ` Tomasz Buchert [this message]
2010-07-19 21:02 ` Daniel Walker
2010-07-19 21:11 ` Tomasz Buchert
2010-07-21 18:03 ` [PATCH 0/4] Wall time clocks + change in access rules Tomasz Buchert
2010-07-21 18:03 ` [PATCH 1/4] posix-timers: Refactoring of CPUCLOCK* macros Tomasz Buchert
2010-07-21 18:03 ` [PATCH 2/4] posix-cpu-timers: Introduction of wall clocks Tomasz Buchert
2010-07-21 18:03 ` [PATCH 3/4] posix-cpu-timers: Wider access to the thread clocks Tomasz Buchert
2010-07-21 18:03 ` [PATCH 4/4] posix-cpu-timers: posix-cpu-timers.c renamed to posix-task-timers.c Tomasz Buchert
-- strict thread matches above, loose matches on Subject: below --
2010-07-30 9:57 [PATCH 0/4] Wall time clocks + change in access rules Tomasz Buchert
2010-07-30 9:57 ` [PATCH 1/4] posix-timers: Refactoring of CPUCLOCK* macros Tomasz Buchert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C44BC9E.30202@inria.fr \
--to=tomasz.buchert@inria.fr \
--cc=dwalker@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sgruszka@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox