From: Kurt Kanzenbach <kurt@linutronix.de>
To: Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>
Cc: John Stultz <john.stultz@linaro.org>,
Stephen Boyd <sboyd@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Richard Cochran <richardcochran@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] timekeeping: Introduce fast accessor to clock tai
Date: Tue, 12 Apr 2022 09:03:42 +0200 [thread overview]
Message-ID: <87v8vepyup.fsf@kurt> (raw)
In-Reply-To: <87k0bvfibm.ffs@tglx>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
On Mon Apr 11 2022, Thomas Gleixner wrote:
> On Sat, Apr 09 2022 at 22:33, Thomas Gleixner wrote:
>> On Sat, Apr 09 2022 at 09:37, Steven Rostedt wrote:
>>> On Sat, 9 Apr 2022 10:12:58 +0200
>>> Kurt Kanzenbach <kurt@linutronix.de> wrote:
>>>
>>>> ---
>>>> include/linux/timekeeping.h | 1 +
>>>> kernel/time/timekeeping.c | 17 +++++++++++++++++
>>>> 2 files changed, 18 insertions(+)
>>>
>>> If the time keeping folks are OK with this and ack it, I'm happy to
>>> take this through my tree.
>>
>> Go ahead. I just sent a Reviewed-by and I don't see conflicting changes
>> in that area. Famous last words :)
>
> And yes, I have some conflicting changes in the pipeline and just saw
> that this lacks a data_race() annotation like the boot variant from
> which this is derived.
Interesting, didn't see that annotation. Anyway, this patch also misses
the corresponding documentation entry. See below.
Thanks,
Kurt
diff --git a/Documentation/core-api/timekeeping.rst b/Documentation/core-api/timekeeping.rst
index 729e24864fe7..22ec68f24421 100644
--- a/Documentation/core-api/timekeeping.rst
+++ b/Documentation/core-api/timekeeping.rst
@@ -132,6 +132,7 @@ Some additional variants exist for more specialized cases:
.. c:function:: u64 ktime_get_mono_fast_ns( void )
u64 ktime_get_raw_fast_ns( void )
u64 ktime_get_boot_fast_ns( void )
+ u64 ktime_get_tai_fast_ns( void )
u64 ktime_get_real_fast_ns( void )
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-04-12 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 8:12 [PATCH 0/3] tracing: Introduce trace clock tai Kurt Kanzenbach
2022-04-09 8:12 ` [PATCH 1/3] timekeeping: Introduce fast accessor to " Kurt Kanzenbach
2022-04-09 13:37 ` Steven Rostedt
2022-04-09 20:33 ` Thomas Gleixner
2022-04-11 20:58 ` Thomas Gleixner
2022-04-12 7:03 ` Kurt Kanzenbach [this message]
2022-04-09 20:32 ` Thomas Gleixner
2022-04-09 8:12 ` [PATCH 2/3] tracing: Introduce trace " Kurt Kanzenbach
2022-04-09 8:13 ` [PATCH 3/3] tracing: Add documentation for " Kurt Kanzenbach
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=87v8vepyup.fsf@kurt \
--to=kurt@linutronix.de \
--cc=corbet@lwn.net \
--cc=john.stultz@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).