[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9b83ce738fc0abde04ad82d0fa6786a1370fbab.camel@perches.com>
Date: Thu, 29 Aug 2019 21:56:44 -0700
From: Joe Perches <joe@...ches.com>
To: shuah <shuah@...nel.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Brendan Higgins <brendanhiggins@...gle.com>
Cc: kunit-dev@...glegroups.com, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, frowand.list@...il.com,
sboyd@...nel.org, pmladek@...e.com, sergey.senozhatsky@...il.com,
rostedt@...dmis.org, Randy Dunlap <rdunlap@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH v2] kunit: fix failure to build without printk
On Thu, 2019-08-29 at 21:44 -0700, Joe Perches wrote:
> On Thu, 2019-08-29 at 11:01 -0600, shuah wrote:
[]
> > WARNING: Prefer [subsystem eg: netdev]_level([subsystem]dev, ... then
> > dev_level(dev, ... then pr_level(... to printk(KERN_LEVEL ...
> > #105: FILE: include/kunit/test.h:343:
> > + printk(KERN_LEVEL "\t# %s: " fmt, (test)->name, ##__VA_ARGS__)
> >
> >
> > Is there supposed to be pr_level() - I can find dev_level()
btw: the checkpatch message is meant to be interpreted as
Prefer [subsystem eg: netdev]_<level>([subsystem]dev, ...) then dev_<level>(dev, ...) then pr_<level>(...), to printk(KERN_<LEVEL> ...)
btw2:
dev_level is actually not a function, but a convenience macro argument
which indirects to an actual specific logging function.
So no, there is not supposed to be a pr_level.
Powered by blists - more mailing lists