From: Thomas Gleixner <tglx@linutronix.de>
To: Kurt Kanzenbach <kurt@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 v2 1/3] timekeeping: Introduce fast accessor to clock tai
Date: Wed, 27 Apr 2022 23:12:58 +0200 [thread overview]
Message-ID: <87mtg6w7qd.ffs@tglx> (raw)
In-Reply-To: <87fslyw94e.fsf@kurt>
On Wed, Apr 27 2022 at 22:42, Kurt Kanzenbach wrote:
> Anyway, with your patch applied [1] and the one below it looks way
> better:
>
> commit 81c4f2de420cc4ac08efc39e78ffd80e146bfbd7
> Author: Kurt Kanzenbach <kurt@linutronix.de>
> Date: Wed Apr 27 21:59:58 2022 +0200
>
> timekeeping: Mark mono fast time accessors as notrace
Can you please post that proper?
> Mark the CLOCK_MONOTONIC fast time accessors as notrace. These functions are
> used in tracing to retrieve timestamps.
>
That lacks a Fixes: tag. These accessors should have been notrace from
day one.
Thanks,
tglx
next prev parent reply other threads:[~2022-04-27 21:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 9:18 [PATCH v2 0/3] tracing: Introduce trace clock tai Kurt Kanzenbach
2022-04-14 9:18 ` [PATCH v2 1/3] timekeeping: Introduce fast accessor to " Kurt Kanzenbach
2022-04-14 14:59 ` Thomas Gleixner
2022-04-18 17:15 ` Steven Rostedt
2022-04-14 15:01 ` [tip: timers/core] " tip-bot2 for Kurt Kanzenbach
2022-04-26 21:53 ` [PATCH v2 1/3] " Steven Rostedt
2022-04-27 8:17 ` Thomas Gleixner
2022-04-27 8:38 ` Kurt Kanzenbach
2022-04-27 15:27 ` Steven Rostedt
2022-04-27 17:22 ` Steven Rostedt
2022-04-27 19:23 ` Steven Rostedt
2022-04-27 20:06 ` Thomas Gleixner
2022-04-27 20:08 ` Steven Rostedt
2022-04-27 20:42 ` Kurt Kanzenbach
2022-04-27 21:05 ` Steven Rostedt
2022-04-27 21:12 ` Thomas Gleixner [this message]
2022-04-14 9:18 ` [PATCH v2 2/3] tracing: Introduce trace " Kurt Kanzenbach
2022-04-14 9:18 ` [PATCH v2 3/3] tracing: Add documentation for " Kurt Kanzenbach
2022-04-14 11:27 ` Bagas Sanjaya
2022-04-14 11:38 ` 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=87mtg6w7qd.ffs@tglx \
--to=tglx@linutronix.de \
--cc=corbet@lwn.net \
--cc=john.stultz@linaro.org \
--cc=kurt@linutronix.de \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.