Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Mon, 23 May 2022 15:24:23 +0100
From:   Chris Down <chris@chrisdown.name>
To:     Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc:     linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Sergey Senozhatsky <senozhatsky@chromium.org>,
        Steven Rostedt <rostedt@goodmis.org>,
        John Ogness <john.ogness@linutronix.de>,
        Geert Uytterhoeven <geert@linux-m68k.org>, kernel-team@fb.com
Subject: Re: [RFC PATCH v2] printk: console: Allow each console to have its
 own loglevel
Message-ID: <YouZF7eWCy8Jrc/O@chrisdown.name>
References: <YoeQLxhDeIk4VSmx@chrisdown.name>
 <20220523130917.GA21282@axis.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <20220523130917.GA21282@axis.com>
User-Agent: Mutt/2.2.5 (a8c7fba1) (2022-05-16)
Precedence: bulk

Hi Vincent,

Vincent Whitchurch writes:
>I've had to do something similar for my systems, to allow all messages
>to always be logged to the pstore console while still allowing the UART
>console loglevel to be adjusted.  I've been carrying the following
>pstore-specific hack for a while now.  This patch set looks like it will
>be able to solve the problem in a generic way.

Thanks, nice to hear about other usecases :-) Yes, this should allow this 
generically for any console, including pstore.