From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752151AbdLEQNv (ORCPT <rfc822;w@1wt.eu>);
        Tue, 5 Dec 2017 11:13:51 -0500
Received: from mail-pf0-f179.google.com ([209.85.192.179]:44323 "EHLO
        mail-pf0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751255AbdLEQNr (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 5 Dec 2017 11:13:47 -0500
X-Google-Smtp-Source: AGs4zMaBgk5pactotN2ET/GkxrGtbdXETc3KBmyEi01IP4tOonaZpdJiVclPegvsrLYzo847ZJu2pA==
Date: Wed, 6 Dec 2017 01:13:43 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
        Kevin Hilman <khilman@baylibre.com>, Mark Brown <broonie@kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Steven Rostedt <rostedt@goodmis.org>,
        Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: kernel CI: printk loglevels in kernel boot logs?
Message-ID: <20171205161343.GA511@tigerII.localdomain>
References: <CAOi56cVORdyjTXK4QGYRfyD1Q=QBgsU3B__gZT0xj6OBKaasLQ@mail.gmail.com>
 <20171122015610.x3kgzqgtwywlurmz@wfg-t540p.sh.intel.com>
 <20171122032702.zd5ouuugrxyemqbh@wfg-t540p.sh.intel.com>
 <20171122113448.sllaehmlqae7telk@pathway.suse.cz>
 <20171122141058.tx2olreq2hhevavk@wfg-t540p.sh.intel.com>
 <20171205155537.w6hohhbvjest3pbm@pathway.suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171205155537.w6hohhbvjest3pbm@pathway.suse.cz>
User-Agent: Mutt/1.9.1 (2017-09-22)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On (12/05/17 16:55), Petr Mladek wrote:
[..]
> 
> Am I too paranoid? Steven? Linus?

well, if there is a tool that believels that there will always be [ (part
of timestamp marker) as the first symbol then that tool has a problem. there
is no "guaranteed" format of console messages. one can print

	pr_err("message\n message\n message\n);

or one can compile the kernel with no CONFIG_PRINTK_TIME.

or one can disable printk_time via printk_time module param.

	-ss