[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <62acd27e418ff202ef2ffedd2474ae7f53f93368.camel@perches.com>
Date: Fri, 07 Oct 2022 08:43:39 -0700
From: Joe Perches <joe@...ches.com>
To: Miquel Raynal <miquel.raynal@...tlin.com>
Cc: Ray Zhang <sgzhang@...gle.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/3] mtd: mtdoops: change printk() to counterpart pr_
functions
On Fri, 2022-10-07 at 09:52 +0200, Miquel Raynal wrote:
> Hi Joe, Ray,
>
> joe@...ches.com wrote on Fri, 07 Oct 2022 00:09:26 -0700:
>
> > On Fri, 2022-10-07 at 06:50 +0000, Ray Zhang wrote:
> > > To comply with latest kernel code requirement, change printk() to
> > > counterpart pr_ functions in mtdoops driver:
> > > - change printk(INFO) to pr_info()
> > > - change printk(DEBUG) to pr_debug()
> >
> > There is a different behavior with printk(KERN_DEBUG to pr_debug(
> > as pr_debug is a no-op unless dynamic debugging is enabled or
> > DEBUG is defined.
>
> I didn't know about this difference. I was expecting printk(KERN_DEBUG)
> to behave the same as pr_debug/dev_dbg.
No worries. Most people do not know this trivia.
I just wanted to inform in case it matters here.
Likely it does not matter.
> But honestly in this driver I feel fine changing the printk(KERN_DEBUG)
> into pr_debug().
Your choice...
Powered by blists - more mailing lists