Re: [tip:core/printk] printk: Add monotonic, boottime, and realtime timestamps

[Thomas Gleixner]

On Tue, 26 Sep 2017, Prarit Bhargava wrote:
> On 09/26/2017 11:26 AM, Thomas Gleixner wrote:
> > On Tue, 26 Sep 2017, Prarit Bhargava wrote:
> > 
> >> On 09/26/2017 04:42 AM, tip-bot for Prarit Bhargava wrote:
> >>> Commit-ID:  310b454a8653ea60d3eb21ce5ab03a282a32fbe1
> >>> Gitweb:     http://git.kernel.org/tip/310b454a8653ea60d3eb21ce5ab03a282a32fbe1
> >>> Author:     Prarit Bhargava <prarit@xxxxxxxxxx>
> >>> AuthorDate: Mon, 18 Sep 2017 13:51:00 -0400
> >>> Committer:  Thomas Gleixner <tglx@xxxxxxxxxxxxx>
> >>> CommitDate: Tue, 26 Sep 2017 10:38:07 +0200
> >>>
> >>> printk: Add monotonic, boottime, and realtime timestamps
> >>>
> >>> printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
> >>> timestamp to printk messages.  The local hardware clock loses time each
> >>> day making it difficult to determine exactly when an issue has occurred in
> >>> the kernel log, and making it difficult to determine how kernel and
> >>> hardware issues relate to each other.
> >>>
> >>> Make printk output different timestamps by adding options for no timestamp,
> >>> the local hardware clock, monotonic clock, boottime clock, and clock
> >>> realtime. The default clock can be selected via:
> >>>
> >>>  - Kconfig
> >>>  - Kernel command line parameter
> >>>  - Sysfs file
> >>>
> >>> Note, that existing user space tools might be confused by selecting clock
> >>> realtime, so handle with care.
> >>
> >> pmladek found a compile warning due to printk_time being unused.  I will post a
> >> v14 on LKML shortly.
> > 
> > Errm. I applied v12. where the heck is v13?
> > 
> > And in the applied patch printk_time is used.....
> 
> Sorry, my mistake I meant v13.
> 
> This morning pmladek posted about a warning when when CONFIG_PRINTK is not defined:
> 
> https://marc.info/?l=linux-doc&m=150642667403344&w=2
> 
> I'm fixing it now for v13.

Please send a delta patch.