[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170722094000.GA8064@xo-6d-61-c0.localdomain>
Date: Sat, 22 Jul 2017 11:40:00 +0200
From: Pavel Machek <pavel@....cz>
To: Mark Salyzyn <salyzyn@...roid.com>
Cc: linux-kernel@...r.kernel.org, andriy.shevchenko@...ux.intel.com,
joe@...ches.com, prarit@...hat.com, rjw@...ysocki.net,
tglx@...utronix.de, Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Kees Cook <keescook@...omium.org>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Tony Luck <tony.luck@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Mark Salyzyn <salyzyn@...gle.com>,
"Luis R. Rodriguez" <mcgrof@...nel.org>,
Nicholas Piggin <npiggin@...il.com>,
Olof Johansson <olof@...om.net>,
"Jason A. Donenfeld" <Jason@...c4.com>,
Josh Poimboeuf <jpoimboe@...hat.com>
Subject: Re: [PATCH v5] printk: Add pr_info_show_time
> For example, the persistent clock that is used to report
> "Suspended for" message, although very useful, is not present on all
> platforms. It is currently standardized for millisecond precision.
Fix that on your platforms, instead?
Pavel
Powered by blists - more mailing lists