From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Clark <robdclark@gmail.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jordan Crouse <jcrouse@codeaurora.org>
Subject: linux-next: build warning after merge of the drm-msm tree
Date: Wed, 1 Nov 2017 14:46:56 +1100 [thread overview]
Message-ID: <20171101144656.691413a2@canb.auug.org.au> (raw)
Hi Rob,
After merging the drm-msm tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
In file included from include/drm/drm_mm.h:49:0,
from include/drm/drmP.h:73,
from drivers/gpu/drm/msm/msm_drv.h:37,
from drivers/gpu/drm/msm/msm_gpu.h:24,
from drivers/gpu/drm/msm/msm_gpu.c:18:
drivers/gpu/drm/msm/msm_gpu.c: In function 'msm_gpu_init':
drivers/gpu/drm/msm/msm_gpu.c:780:31: warning: format '%lu' expects argument of type 'long unsigned int', but argument 7 has type 'unsigned int' [-Wformat=]
DRM_DEV_INFO_ONCE(drm->dev, "Only creating %lu ringbuffers\n",
^
include/drm/drm_print.h:237:60: note: in definition of macro 'DRM_DEV_INFO'
drm_dev_printk(dev, KERN_INFO, DRM_UT_NONE, __func__, "", fmt, \
^
drivers/gpu/drm/msm/msm_gpu.c:780:3: note: in expansion of macro 'DRM_DEV_INFO_ONCE'
DRM_DEV_INFO_ONCE(drm->dev, "Only creating %lu ringbuffers\n",
^
Introduced by commit
f97decac5f4c ("drm/msm: Support multiple ringbuffers")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-11-01 3:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 3:46 Stephen Rothwell [this message]
2017-11-01 15:19 ` linux-next: build warning after merge of the drm-msm tree Rob Clark
-- strict thread matches above, loose matches on Subject: below --
2020-09-21 3:16 Stephen Rothwell
2020-09-14 2:10 Stephen Rothwell
2020-09-17 7:58 ` Stephen Rothwell
2017-08-03 3:12 Stephen Rothwell
2017-08-03 3:09 Stephen Rothwell
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=20171101144656.691413a2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jcrouse@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robdclark@gmail.com \
/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).