[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1707190035270.2425@nanos>
Date: Wed, 19 Jul 2017 00:36:49 +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, andy.shevchenko@...il.com,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Mark Salyzyn <salyzyn@...gle.com>,
Thierry Strudel <tstrudel@...gle.com>,
John Stultz <john.stultz@...aro.org>,
Josh Triplett <josh@...htriplett.org>,
Nicolas Pitre <nicolas.pitre@...aro.org>,
Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH v3 1/4] time: rtc-lib: Add rtc_show_time(const char
*prefix_msg)
On Tue, 18 Jul 2017, Mark Salyzyn wrote:
> Go directly to the rtc for persistent wall clock time and print.
> Useful if REALTIME is required to be logged in a low level power
> management function or when clock activities are suspended. An
> aid to permit user space alignment of kernel activities.
Can you please spare the churn and wait until the discussion about the
general issues is resolved before sending out yet another set of patches,
which do not address any of the real important questions?
Thanks,
tglx
Powered by blists - more mailing lists