Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 2 Jan 2023 16:15:03 +0100
From:   Petr Mladek <pmladek@suse.com>
To:     John Ogness <john.ogness@linutronix.de>
Cc:     Sergey Senozhatsky <senozhatsky@chromium.org>,
        Steven Rostedt <rostedt@goodmis.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH printk v3 4/6] printk: introduce struct console_buffers
Message-ID: <Y7LyHpHlLc3J+zXk@alley>
References: <20221221202704.857925-1-john.ogness@linutronix.de>
 <20221221202704.857925-5-john.ogness@linutronix.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221221202704.857925-5-john.ogness@linutronix.de>
Precedence: bulk

On Wed 2022-12-21 21:33:02, John Ogness wrote:
> Introduce a new struct console_buffers to contain all the buffers
> needed to read and format a printk message for console output.
> Putting the buffers inside a struct reduces the number of buffer
> pointers that need to be tracked. Also, it allows usage of the
> sizeof() macro for the buffer sizes, rather than expecting certain
> sized buffers being passed in.
> 
> Note that since the output buffer for normal consoles is now
> CONSOLE_EXT_LOG_MAX instead of CONSOLE_LOG_MAX, multi-line
> messages that may have been previously truncated will now be
> printed in full. This should be considered a feature and not a bug
> since the CONSOLE_LOG_MAX restriction was about limiting static
> buffer usage rather than limiting printed text.
> 
> Signed-off-by: John Ogness <john.ogness@linutronix.de>

Reviewed-by: Petr Mladek <pmladek@suse.com>

Thanks for renaming the buffers. I believe that it will make
the code easier to follow in the long term.

Best Regards,
Petr