All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Petr Mladek <pmladek@suse.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
	John Ogness <john.ogness@linutronix.de>,
	Orson Zhai <orson.zhai@unisoc.com>, Baoquan He <bhe@redhat.com>,
	cixi.geng1@unisoc.com, Stephen Boyd <sboyd@kernel.org>,
	zhang.lyra@gmail.com, Steven Sistare <steven.sistare@oracle.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Jon DeVree <nuxi@vault24.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	John Stultz <john.stultz@linaro.org>,
	ruifeng.zhang1@unisoc.com, Orson Zhai <orsonzhai@gmail.com>,
	Salvatore Bonaccorso <carnil@debian.org>,
	Dave Young <dyoung@redhat.com>,
	Dominique Martinet <asmadeus@codewreck.org>,
	Vivek Goyal <vgoyal@redhat.com>,
	Pavel Tatashin <pasha.tatashin@soleen.com>
Subject: Re: [RFC PATCH] printk: Change timestamp to triplet as mono, boot and real
Date: Thu, 13 Aug 2020 12:26:03 +0200	[thread overview]
Message-ID: <87k0y2lu4k.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200813015500.GC2020879@jagdpanzerIV.localdomain>

Sergey Senozhatsky <sergey.senozhatsky@gmail.com> writes:
> On (20/08/11 15:02), Petr Mladek wrote:
>> There is still the alternative to print all three timestamps regularly
>> for those interested. It is less user convenient but much easier
>> to maintain.
>
> Yes, that's a nice alternative.

It's trivial on the kernel side, annoying for all people who do not care
about them because they show up in syslog and it's a fricking nightmare
to reconstruct over a large cluster of machines.

Thanks,

        tglx

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Petr Mladek <pmladek@suse.com>
Cc: Orson Zhai <orsonzhai@gmail.com>,
	Prarit Bhargava <prarit@redhat.com>,
	Dave Young <dyoung@redhat.com>, Baoquan He <bhe@redhat.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Stultz <john.stultz@linaro.org>,
	Stephen Boyd <sboyd@kernel.org>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	zhang.lyra@gmail.com, ruifeng.zhang1@unisoc.com,
	cixi.geng1@unisoc.com, Orson Zhai <orson.zhai@unisoc.com>,
	Pavel Tatashin <pasha.tatashin@soleen.com>,
	Steven Sistare <steven.sistare@oracle.com>,
	Dominique Martinet <asmadeus@codewreck.org>,
	Jon DeVree <nuxi@vault24.org>,
	Salvatore Bonaccorso <carnil@debian.org>,
	John Ogness <john.ogness@linutronix.de>
Subject: Re: [RFC PATCH] printk: Change timestamp to triplet as mono, boot and real
Date: Thu, 13 Aug 2020 12:26:03 +0200	[thread overview]
Message-ID: <87k0y2lu4k.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200813015500.GC2020879@jagdpanzerIV.localdomain>

Sergey Senozhatsky <sergey.senozhatsky@gmail.com> writes:
> On (20/08/11 15:02), Petr Mladek wrote:
>> There is still the alternative to print all three timestamps regularly
>> for those interested. It is less user convenient but much easier
>> to maintain.
>
> Yes, that's a nice alternative.

It's trivial on the kernel side, annoying for all people who do not care
about them because they show up in syslog and it's a fricking nightmare
to reconstruct over a large cluster of machines.

Thanks,

        tglx

  parent reply	other threads:[~2020-08-13 10:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  4:40 [RFC PATCH] printk: Change timestamp to triplet as mono, boot and real Orson Zhai
2020-08-11  4:40 ` Orson Zhai
2020-08-11  4:56 ` Randy Dunlap
2020-08-11  4:56   ` Randy Dunlap
2020-08-11  9:44 ` Petr Mladek
2020-08-11  9:44   ` Petr Mladek
2020-08-11 12:05   ` Thomas Gleixner
2020-08-11 12:05     ` Thomas Gleixner
2020-08-11 13:02     ` Petr Mladek
2020-08-11 13:02       ` Petr Mladek
2020-08-11 13:43       ` Prarit Bhargava
2020-08-11 13:43         ` Prarit Bhargava
2020-08-13  1:55       ` Sergey Senozhatsky
2020-08-13  1:55         ` Sergey Senozhatsky
2020-08-13 10:22         ` Petr Mladek
2020-08-13 10:22           ` Petr Mladek
2020-08-13 11:31           ` Sergey Senozhatsky
2020-08-13 11:31             ` Sergey Senozhatsky
2020-08-14  9:50             ` Petr Mladek
2020-08-14  9:50               ` Petr Mladek
2020-08-13 10:26         ` Thomas Gleixner [this message]
2020-08-13 10:26           ` Thomas Gleixner
2020-08-14  6:34 ` Dave Young
2020-08-14  6:34   ` Dave Young

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=87k0y2lu4k.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=asmadeus@codewreck.org \
    --cc=bhe@redhat.com \
    --cc=carnil@debian.org \
    --cc=cixi.geng1@unisoc.com \
    --cc=dyoung@redhat.com \
    --cc=john.ogness@linutronix.de \
    --cc=john.stultz@linaro.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuxi@vault24.org \
    --cc=orson.zhai@unisoc.com \
    --cc=orsonzhai@gmail.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=pmladek@suse.com \
    --cc=prarit@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=ruifeng.zhang1@unisoc.com \
    --cc=sboyd@kernel.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=steven.sistare@oracle.com \
    --cc=vgoyal@redhat.com \
    --cc=zhang.lyra@gmail.com \
    /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.