[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1707190002300.2425@nanos>
Date: Wed, 19 Jul 2017 00:06:39 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Mark Salyzyn <salyzyn@...roid.com>
cc: linux-kernel@...r.kernel.org, rjw@...ysocki.net,
len.brown@...el.com, pavel@....cz, linux-pm@...r.kernel.org,
a.zummo@...ertech.it, alexandre.belloni@...e-electrons.com,
linux-rtc@...r.kernel.org, Mark Salyzyn <salyzyn@...gle.com>,
Thierry Strudel <tstrudel@...gle.com>
Subject: Re: [PATCH v2 2/4] time: Print wall time at die and reboot
On Tue, 18 Jul 2017, Mark Salyzyn wrote:
> Permits power state and battery life diagnosis.
This changelog is useless as long as you do not explain in which whay that
permits power state and battery life diagnosis.
I really have a hard time to figure out why you need to print RTC time on
oops or any of the other actions. That whole thing looks pretty
overengineered for a dubious value.
What kind of information is the current stuff missing and how are you using
this new information for better diagnosis?
Thanks,
tglx
Powered by blists - more mailing lists