[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZJqxpBh3ppSkugd9@lothringen>
Date: Tue, 27 Jun 2023 11:53:40 +0200
From: Frederic Weisbecker <frederic@...nel.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
Anna-Maria Behnsen <anna-maria@...utronix.de>,
John Stultz <jstultz@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
Stephen Boyd <sboyd@...nel.org>,
Eric Biederman <ebiederm@...ssion.com>,
Oleg Nesterov <oleg@...hat.com>
Subject: Re: [patch 10/45] posix-cpu-timers: Use @now instead of @val for
clarity
On Tue, Jun 06, 2023 at 04:37:34PM +0200, Thomas Gleixner wrote:
> posix_cpu_timer_set() uses @val as variable for the current time. That's
> confusing at best.
>
> Use @now as anywhere else and rewrite the confusing comment about clock
> sampling.
>
> No functional change.
>
> Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
Reviewed-by: Frederic Weisbecker <frederic@...nel.org>
Powered by blists - more mailing lists