From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ioannis Valasakis <code@wizofe.uk>
Subject: Re: linux-next: build warning after merge of the staging tree
Date: Thu, 8 Nov 2018 03:17:31 -0800 [thread overview]
Message-ID: <20181108111731.GA32115@kroah.com> (raw)
In-Reply-To: <20181108133307.5cca74cb@canb.auug.org.au>
On Thu, Nov 08, 2018 at 01:33:07PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from include/linux/printk.h:336,
> from include/linux/kernel.h:14,
> from include/linux/clk.h:16,
> from drivers/staging/media/tegra-vde/tegra-vde.c:12:
> drivers/staging/media/tegra-vde/tegra-vde.c: In function 'tegra_vde_setup_iram_tables':
> drivers/staging/media/tegra-vde/tegra-vde.c:265:5: warning: format '%d' expects argument of type 'int', but argument 6 has type 'long unsigned int' [-Wformat=]
> "\tFrame %d: frame_num = %d B_frame = %d\n",
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> include/linux/dynamic_debug.h:135:39: note: in definition of macro 'dynamic_dev_dbg'
> __dynamic_dev_dbg(&descriptor, dev, fmt, \
> ^~~
> include/linux/device.h:1463:23: note: in expansion of macro 'dev_fmt'
> dynamic_dev_dbg(dev, dev_fmt(fmt), ##__VA_ARGS__)
> ^~~~~~~
> drivers/staging/media/tegra-vde/tegra-vde.c:264:4: note: in expansion of macro 'dev_dbg'
> dev_dbg(vde->miscdev.parent,
> ^~~~~~~
>
> Introduced by commit
>
> 42e764d05712 ("staging: tegravde: replace bit assignment with macro")
I saw this warning, and ignored it, my fault. Colin just sent a patch
for this so I'll queue that up now, thanks.
greg k-h
next prev parent reply other threads:[~2018-11-08 11:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 2:33 linux-next: build warning after merge of the staging tree Stephen Rothwell
2018-11-08 11:17 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-09 7:16 Stephen Rothwell
2020-09-09 7:41 ` Greg KH
2019-12-13 1:10 Stephen Rothwell
2019-08-26 6:24 Stephen Rothwell
2019-08-26 6:30 ` Greg KH
2019-08-26 8:38 ` Gao Xiang
2019-08-26 8:54 ` Gao Xiang
2019-08-26 9:43 ` Gao Xiang
2019-08-26 9:53 ` Gao Xiang
2019-08-26 11:13 ` Gao Xiang
2019-08-14 6:08 Stephen Rothwell
2019-08-14 7:42 ` Greg KH
2019-04-23 5:13 Stephen Rothwell
2018-09-03 2:06 Stephen Rothwell
2018-09-04 9:04 ` John Whitmore
2018-05-14 4:37 Stephen Rothwell
2018-01-16 2:45 Stephen Rothwell
2018-01-16 5:59 ` Greg KH
2018-01-16 10:47 ` Arnd Bergmann
2018-01-16 15:02 ` Greg KH
2017-01-20 4:36 Stephen Rothwell
2017-01-20 8:37 ` Greg KH
2017-01-20 9:18 ` Linus Walleij
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=20181108111731.GA32115@kroah.com \
--to=greg@kroah.com \
--cc=code@wizofe.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).