[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251217110443.0274c2be@gandalf.local.home>
Date: Wed, 17 Dec 2025 11:04:43 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Joel Granados <joel.granados@...nel.org>, Petr Mladek
<pmladek@...e.com>, Chris Down <chris@...isdown.name>,
linux-kernel@...r.kernel.org, Greg Kroah-Hartman
<gregkh@...uxfoundation.org>, Sergey Senozhatsky
<senozhatsky@...omium.org>, John Ogness <john.ogness@...utronix.de>, Tony
Lindgren <tony.lindgren@...ux.intel.com>, kernel-team@...com
Subject: Re: [PATCH v8 20/21] printk: Deprecate the kernel.printk sysctl
interface
On Wed, 17 Dec 2025 15:33:42 +0100
Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> > > OK, what about the following?
> > >
> > > pr_warn_once("printk: The kernel.printk sysctl is deprecated and will be removed in 2036.\n");
> > > pr_warn_once("printk: Use kernel.console_loglevel or kernel.default_message_loglevel instead.\n");
> > I meant it more as a long line in the code. Not a long line in the
> > log. Like this:
> >
> > pr_warn_once("printk: The kernel.printk sysctl is deprecated. Instead, use "
> > "kernel.console_loglevel or kernel.default_message_loglevel.\n");
> >
> > Its still long, but more manageable.
>
> Please do not split long messages, as it makes it harder to find them
> in the source tree.
Right. Linus has stated that strings should not be split just because they
go over the column limit.
-- Steve
Powered by blists - more mailing lists