linux-kernel - Re: design: was: Re: [RFC PATCH v2] printk: console: Allow each console to have its own loglevel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Ys7brwCVmQ2iH9xK@chrisdown.name>
Date:   Wed, 13 Jul 2022 15:50:23 +0100
From:   Chris Down <chris@...isdown.name>
To:     Petr Mladek <pmladek@...e.com>
Cc:     John Ogness <john.ogness@...utronix.de>,
        linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Sergey Senozhatsky <senozhatsky@...omium.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Geert Uytterhoeven <geert@...ux-m68k.org>, kernel-team@...com
Subject: Re: design: was: Re: [RFC PATCH v2] printk: console: Allow each
 console to have its own loglevel

Petr Mladek writes:
>> Of course, it would mean that the type of option would need to be
>> specified. Something like:
>>
>> console=ttyS0,115200n8,loglevel=3
>
>I like this. It is longer but it makes the meaning very obvious.

Yes, this looks good to me and I'll implement it for v3. Thanks!

>I just think about using ':' instead of '=' to distinguish
>the assignment of outer 'console' vs the inner 'loglevel' parameters.

Agreed, I'll use ":".