From: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>
To: tglx@linutronix.de
Cc: Llillian@star-ark.net, agordeev@linux.ibm.com,
akpm@linux-foundation.org, alexander.shishkin@linux.intel.com,
anna-maria@linutronix.de, bigeasy@linutronix.de,
catalin.marinas@arm.com, chenhuacai@kernel.org,
francesco@valla.it, frederic@kernel.org,
guoweikang.kernel@gmail.com, jstultz@google.com,
kpsingh@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
maz@kernel.org, mingo@kernel.org, pmladek@suse.com,
rrangel@chromium.org, sboyd@kernel.org, urezki@gmail.com,
v-singh1@ti.com, will@kernel.org, peterz@infradead.org,
elver@google.com, namcao@linutronix.de
Subject: Re: [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp
Date: Tue, 2 Sep 2025 19:09:08 +0530 [thread overview]
Message-ID: <20250902133920.973210-1-kaiwan.billimoria@gmail.com> (raw)
In-Reply-To: <871pp14pkr.ffs@tglx>
Subject: Re: [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp
> Under the assumption that nothing on the way resets the counter.
Ah. Is there any known component - within ROM/BL stages/kernel code - that does
this?
Forgive my asking, but if fine, will this (above-mentioned) patch be taken? So,
knowing that, we can proceed forward..
Thanks,
Kaiwan.
next prev parent reply other threads:[~2025-09-02 21:42 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
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 [this message]
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=20250902133920.973210-1-kaiwan.billimoria@gmail.com \
--to=kaiwan.billimoria@gmail.com \
--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=elver@google.com \
--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=namcao@linutronix.de \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rrangel@chromium.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--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.