LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
Kevin Hilman <khilman@baylibre.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Petr Mladek <pmladek@suse.com>,
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?
Date: Wed, 22 Nov 2017 10:42:55 +0000 [thread overview]
Message-ID: <20171122104255.b6qz4f7m2utaiwha@sirena.org.uk> (raw)
In-Reply-To: <20171122052630.GA447@jagdpanzerIV>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
On Wed, Nov 22, 2017 at 02:26:30PM +0900, Sergey Senozhatsky wrote:
> so may be we can add "syslog" mode for console drivers and do print_prefix()
> in console_unlock() [unless have nr_ext_console_drivers]. if this is what
> you guys are talking about. (frankly, I have no idea if there are tools
> that parse output from serial consoles/net consoles and thus might get
> confused by extra <%u> in every message).
In this case the goal is actually to use this with tools parsing the
serial console output - it's in the context of kernelci where the boot
logs are most interesting when we fail to get to the point of being able
to look in /proc. Kevin's initial proposal was to have a command line
option.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-11-22 10:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOi56cVORdyjTXK4QGYRfyD1Q=QBgsU3B__gZT0xj6OBKaasLQ@mail.gmail.com>
[not found] ` <20171122015610.x3kgzqgtwywlurmz@wfg-t540p.sh.intel.com>
2017-11-22 3:27 ` kernel CI: printk loglevels in kernel boot logs? Fengguang Wu
2017-11-22 5:26 ` Sergey Senozhatsky
2017-11-22 10:42 ` Mark Brown [this message]
2017-11-22 11:34 ` Petr Mladek
2017-11-22 12:38 ` Sergey Senozhatsky
2017-11-22 12:52 ` Fengguang Wu
2017-11-23 2:59 ` Sergey Senozhatsky
2017-11-23 3:14 ` Fengguang Wu
2017-11-23 4:31 ` Sergey Senozhatsky
2017-11-29 0:13 ` Kevin Hilman
2017-11-29 7:25 ` Sergey Senozhatsky
2017-11-30 17:45 ` Kevin Hilman
2017-12-01 1:25 ` Sergey Senozhatsky
2017-11-23 10:04 ` Petr Mladek
2017-11-22 20:22 ` Kevin Hilman
2017-11-22 14:10 ` Fengguang Wu
2017-12-05 15:55 ` Petr Mladek
2017-12-05 16:13 ` Sergey Senozhatsky
2017-12-05 20:54 ` Steven Rostedt
2017-12-06 13:54 ` Petr Mladek
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=20171122104255.b6qz4f7m2utaiwha@sirena.org.uk \
--to=broonie@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).