From: kernel test robot <lkp@intel.com>
To: Zack Rusin <zackr@vmware.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Martin Krastev <krastevm@vmware.com>
Subject: [drm-misc:for-linux-next 4/12] drivers/gpu/drm/vmwgfx/vmwgfx_gem.c:230:33: warning: format '%ld' expects argument of type 'long int', but argument 4 has type 'size_t' {aka 'unsigned int'}
Date: Fri, 10 Dec 2021 09:11:17 +0800 [thread overview]
Message-ID: <202112100931.0DNGyGGp-lkp@intel.com> (raw)
tree: git://anongit.freedesktop.org/drm/drm-misc for-linux-next
head: 94eb7de6f4bec1c8bb99371c21df42cac0de6ee9
commit: 8afa13a0583f94c14607e3041c02f068ac8fb628 [4/12] drm/vmwgfx: Implement DRIVER_GEM
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20211210/202112100931.0DNGyGGp-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
git remote add drm-misc git://anongit.freedesktop.org/drm/drm-misc
git fetch --no-tags drm-misc for-linux-next
git checkout 8afa13a0583f94c14607e3041c02f068ac8fb628
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/gpu/drm/vmwgfx/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/gpu/drm/vmwgfx/vmwgfx_gem.c: In function 'vmw_bo_print_info':
>> drivers/gpu/drm/vmwgfx/vmwgfx_gem.c:230:33: warning: format '%ld' expects argument of type 'long int', but argument 4 has type 'size_t' {aka 'unsigned int'} [-Wformat=]
230 | seq_printf(m, "\t\t0x%08x: %12ld bytes %s, type = %s",
| ~~~~^
| |
| long int
| %12d
231 | id, bo->base.base.size, placement, type);
| ~~~~~~~~~~~~~~~~~~
| |
| size_t {aka unsigned int}
vim +230 drivers/gpu/drm/vmwgfx/vmwgfx_gem.c
188
189 static void vmw_bo_print_info(int id, struct vmw_buffer_object *bo, struct seq_file *m)
190 {
191 const char *placement;
192 const char *type;
193
194 switch (bo->base.resource->mem_type) {
195 case TTM_PL_SYSTEM:
196 placement = " CPU";
197 break;
198 case VMW_PL_GMR:
199 placement = " GMR";
200 break;
201 case VMW_PL_MOB:
202 placement = " MOB";
203 break;
204 case VMW_PL_SYSTEM:
205 placement = "VCPU";
206 break;
207 case TTM_PL_VRAM:
208 placement = "VRAM";
209 break;
210 default:
211 placement = "None";
212 break;
213 }
214
215 switch (bo->base.type) {
216 case ttm_bo_type_device:
217 type = "device";
218 break;
219 case ttm_bo_type_kernel:
220 type = "kernel";
221 break;
222 case ttm_bo_type_sg:
223 type = "sg ";
224 break;
225 default:
226 type = "none ";
227 break;
228 }
229
> 230 seq_printf(m, "\t\t0x%08x: %12ld bytes %s, type = %s",
231 id, bo->base.base.size, placement, type);
232 seq_printf(m, ", priority = %u, pin_count = %u, GEM refs = %d, TTM refs = %d",
233 bo->base.priority,
234 bo->base.pin_count,
235 kref_read(&bo->base.base.refcount),
236 kref_read(&bo->base.kref));
237 seq_puts(m, "\n");
238 }
239
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-10 1:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202112100931.0DNGyGGp-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=krastevm@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zackr@vmware.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
all inboxes | Powered by JetHome®