From: Greg KH <greg@kroah•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Arnd Bergmann <arnd@arndb•de>, Jim Cromie <jim.cromie@gmail•com>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the char-misc.current tree
Date: Wed, 9 Sep 2020 14:22:25 +0200 [thread overview]
Message-ID: <20200909122225.GA668220@kroah.com> (raw)
In-Reply-To: <20200908094317.6dc1cb2a@canb.auug.org.au>
On Tue, Sep 08, 2020 at 09:43:17AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the char-misc.current tree, today's linux-next build
> (x86_64 allmodconfig) produced this warning:
>
> In file included from include/linux/printk.h:7,
> from include/linux/kernel.h:15,
> from lib/dynamic_debug.c:16:
> lib/dynamic_debug.c: In function 'ddebug_parse_query':
> include/linux/kern_levels.h:5:18: warning: format '%s' expects a matching 'char *' argument [-Wformat=]
> 5 | #define KERN_SOH "\001" /* ASCII Start Of Header */
> | ^~~~~~
> include/linux/kern_levels.h:14:19: note: in expansion of macro 'KERN_SOH'
> 14 | #define KERN_INFO KERN_SOH "6" /* informational */
> | ^~~~~~~~
> include/linux/printk.h:369:9: note: in expansion of macro 'KERN_INFO'
> 369 | printk(KERN_INFO pr_fmt(fmt), ##__VA_ARGS__)
> | ^~~~~~~~~
> lib/dynamic_debug.c:116:3: note: in expansion of macro 'pr_info'
> 116 | pr_info(fmt, ##__VA_ARGS__); \
> | ^~~~~~~
> lib/dynamic_debug.c:119:28: note: in expansion of macro 'vnpr_info'
> 119 | #define vpr_info(fmt, ...) vnpr_info(1, fmt, ##__VA_ARGS__)
> | ^~~~~~~~~
> lib/dynamic_debug.c:388:3: note: in expansion of macro 'vpr_info'
> 388 | vpr_info("module:%s queries:'%s'\n", modname);
> | ^~~~~~~~
>
> Introduced by commit
>
> 42f07816ac0c ("dyndbg: fix problem parsing format="foo bar"")
Odd it doesn't show up in my builds, or in 0-day :(
Jim, can you send a fix for this, or is this due to some other tree's
issues?
thanks,
greg k-h
next prev parent reply other threads:[~2020-09-09 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 23:43 linux-next: build warning after merge of the char-misc.current tree Stephen Rothwell
2020-09-09 12:22 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-22 22:22 Stephen Rothwell
2019-07-22 23:31 ` Mauro Rossi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200909122225.GA668220@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=jim.cromie@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox