From: Thomas Gleixner <tglx@linutronix.de>
To: vishnu singh <v-singh1@ti.com>,
mark.rutland@arm.com, maz@kernel.org, catalin.marinas@arm.com,
will@kernel.org, jstultz@google.com, sboyd@kernel.org,
akpm@linux-foundation.org, chenhuacai@kernel.org,
pmladek@suse.com, agordeev@linux.ibm.com, bigeasy@linutronix.de,
urezki@gmail.com, Llillian@star-ark.net, francesco@valla.it,
guoweikang.kernel@gmail.com, alexander.shishkin@linux.intel.com,
rrangel@chromium.org, kpsingh@kernel.org,
anna-maria@linutronix.de, mingo@kernel.org, frederic@kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp
Date: Sun, 24 Aug 2025 01:12:17 +0200 [thread overview]
Message-ID: <87y0r93a5q.ffs@tglx> (raw)
In-Reply-To: <871pp14pkr.ffs@tglx>
On Sun, Aug 24 2025 at 00:53, Thomas Gleixner wrote:
> So the [0.000008] timestamp happens exactly 1.0 seconds after power
> on.
Let me correct myself it's exactly: 1.000008 seconds after power on
Sorry for this fundamental mistake.
Thanks,
tglx
next prev parent reply other threads:[~2025-08-23 23:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 4:40 [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp vishnu singh
2025-08-23 22:53 ` Thomas Gleixner
2025-08-23 23:12 ` Thomas Gleixner [this message]
2025-09-01 4:05 ` Kaiwan N Billimoria
2025-09-01 5:57 ` Kaiwan N Billimoria
2025-09-02 7:02 ` [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp Kaiwan N Billimoria
2025-09-02 10:52 ` Thomas Gleixner
2025-09-02 13:39 ` Kaiwan N Billimoria
2025-09-02 21:32 ` Thomas Gleixner
2025-08-24 4:35 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2025-08-23 4:19 vishnu singh
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=87y0r93a5q.ffs@tglx \
--to=tglx@linutronix.de \
--cc=Llillian@star-ark.net \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=anna-maria@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=francesco@valla.it \
--cc=frederic@kernel.org \
--cc=guoweikang.kernel@gmail.com \
--cc=jstultz@google.com \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mingo@kernel.org \
--cc=pmladek@suse.com \
--cc=rrangel@chromium.org \
--cc=sboyd@kernel.org \
--cc=urezki@gmail.com \
--cc=v-singh1@ti.com \
--cc=will@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.