[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zd-O-6q3HcQewIrA@smile.fi.intel.com>
Date: Wed, 28 Feb 2024 21:52:27 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Chris Down <chris@...isdown.name>, Petr Mladek <pmladek@...e.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jessica Yu <jeyu@...nel.org>, Steven Rostedt <rostedt@...dmis.org>,
John Ogness <john.ogness@...utronix.de>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Jason Baron <jbaron@...mai.com>, Jim Cromie <jim.cromie@...il.com>,
Ilya Dryomov <idryomov@...il.com>, Xiubo Li <xiubli@...hat.com>,
Jeff Layton <jlayton@...nel.org>, linux-kernel@...r.kernel.org,
ceph-devel@...r.kernel.org
Subject: Re: [PATCH 2/4] dev_printk: Add and use dev_no_printk()
On Wed, Feb 28, 2024 at 08:33:19PM +0100, Geert Uytterhoeven wrote:
> On Wed, Feb 28, 2024 at 6:39 PM Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com> wrote:
> > On Wed, Feb 28, 2024 at 03:00:03PM +0100, Geert Uytterhoeven wrote:
..
> > dev_printk()
>
> I fully agree. But the surrounding comments don't, so I gave in.
Is there any better justification to keep a technical debt?
I mean, the comment here can be better than existed ones, if you feel
uncomfortable with it, you can fix the rest in a separate patch.
Would it be a big deal? :-)
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists