From: kernel test robot <lkp@intel.com>
To: "Chen-Yu Tsai" <wenst@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
Inki Dae <inki.dae@samsung.com>
Subject: [daeinki-drm-exynos:exynos-drm-next 3/4] drivers/gpu/drm/exynos/exynos_drm_gem.c:69:49: warning: format '%lx' expects argument of type 'long unsigned int', but argument 6 has type 'size_t' {aka 'unsigned int'}
Date: Wed, 08 Apr 2026 13:14:02 +0800 [thread overview]
Message-ID: <202604081331.jSJQSVmg-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next
head: 0867757f1eec0a246c70b2407a1bbed949170821
commit: 11e898373fba6b1d27b15ab4beff592701a57293 [3/4] drm/exynos: Drop exynos_drm_gem.size field
config: nios2-allmodconfig (https://download.01.org/0day-ci/archive/20260408/202604081331.jSJQSVmg-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260408/202604081331.jSJQSVmg-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202604081331.jSJQSVmg-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/exynos/exynos_drm_gem.c:16:
drivers/gpu/drm/exynos/exynos_drm_gem.c: In function 'exynos_drm_alloc_buf':
>> drivers/gpu/drm/exynos/exynos_drm_gem.c:69:49: warning: format '%lx' expects argument of type 'long unsigned int', but argument 6 has type 'size_t' {aka 'unsigned int'} [-Wformat=]
69 | DRM_DEV_DEBUG_KMS(drm_dev_dma_dev(dev), "dma_addr(0x%lx), size(0x%lx)\n",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
70 | (unsigned long)exynos_gem->dma_addr, exynos_gem->base.size);
| ~~~~~~~~~~~~~~~~~~~~~
| |
| size_t {aka unsigned int}
include/drm/drm_print.h:563:39: note: in definition of macro 'drm_dev_dbg'
563 | __drm_dev_dbg(NULL, dev, cat, fmt, ##__VA_ARGS__)
| ^~~
drivers/gpu/drm/exynos/exynos_drm_gem.c:69:9: note: in expansion of macro 'DRM_DEV_DEBUG_KMS'
69 | DRM_DEV_DEBUG_KMS(drm_dev_dma_dev(dev), "dma_addr(0x%lx), size(0x%lx)\n",
| ^~~~~~~~~~~~~~~~~
drivers/gpu/drm/exynos/exynos_drm_gem.c:69:76: note: format string is defined here
69 | DRM_DEV_DEBUG_KMS(drm_dev_dma_dev(dev), "dma_addr(0x%lx), size(0x%lx)\n",
| ~~^
| |
| long unsigned int
| %x
In file included from drivers/gpu/drm/exynos/exynos_drm_gem.c:16:
drivers/gpu/drm/exynos/exynos_drm_gem.c: In function 'exynos_drm_free_buf':
drivers/gpu/drm/exynos/exynos_drm_gem.c:83:37: warning: format '%lx' expects argument of type 'long unsigned int', but argument 6 has type 'size_t' {aka 'unsigned int'} [-Wformat=]
83 | DRM_DEV_DEBUG_KMS(dev->dev, "dma_addr(0x%lx), size(0x%lx)\n",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
84 | (unsigned long)exynos_gem->dma_addr, exynos_gem->base.size);
| ~~~~~~~~~~~~~~~~~~~~~
| |
| size_t {aka unsigned int}
include/drm/drm_print.h:563:39: note: in definition of macro 'drm_dev_dbg'
563 | __drm_dev_dbg(NULL, dev, cat, fmt, ##__VA_ARGS__)
| ^~~
drivers/gpu/drm/exynos/exynos_drm_gem.c:83:9: note: in expansion of macro 'DRM_DEV_DEBUG_KMS'
83 | DRM_DEV_DEBUG_KMS(dev->dev, "dma_addr(0x%lx), size(0x%lx)\n",
| ^~~~~~~~~~~~~~~~~
drivers/gpu/drm/exynos/exynos_drm_gem.c:83:64: note: format string is defined here
83 | DRM_DEV_DEBUG_KMS(dev->dev, "dma_addr(0x%lx), size(0x%lx)\n",
| ~~^
| |
| long unsigned int
| %x
vim +69 drivers/gpu/drm/exynos/exynos_drm_gem.c
2043e6f6d5c5fb0 Thomas Zimmermann 2021-11-08 26
9940d9d93406f41 Marek Szyprowski 2020-04-23 27 static int exynos_drm_alloc_buf(struct exynos_drm_gem *exynos_gem, bool kvmap)
2a8cb4894540898 Joonyoung Shim 2015-08-16 28 {
813fd67b57ffca0 Joonyoung Shim 2015-10-02 29 struct drm_device *dev = exynos_gem->base.dev;
9940d9d93406f41 Marek Szyprowski 2020-04-23 30 unsigned long attr = 0;
2a8cb4894540898 Joonyoung Shim 2015-08-16 31
813fd67b57ffca0 Joonyoung Shim 2015-10-02 32 if (exynos_gem->dma_addr) {
e457a1a9585b941 Chen-Yu Tsai 2026-03-26 33 DRM_DEV_DEBUG_KMS(drm_dev_dma_dev(dev), "already allocated.\n");
2a8cb4894540898 Joonyoung Shim 2015-08-16 34 return 0;
2a8cb4894540898 Joonyoung Shim 2015-08-16 35 }
2a8cb4894540898 Joonyoung Shim 2015-08-16 36
2a8cb4894540898 Joonyoung Shim 2015-08-16 37 /*
2a8cb4894540898 Joonyoung Shim 2015-08-16 38 * if EXYNOS_BO_CONTIG, fully physically contiguous memory
2a8cb4894540898 Joonyoung Shim 2015-08-16 39 * region will be allocated else physically contiguous
2a8cb4894540898 Joonyoung Shim 2015-08-16 40 * as possible.
2a8cb4894540898 Joonyoung Shim 2015-08-16 41 */
813fd67b57ffca0 Joonyoung Shim 2015-10-02 42 if (!(exynos_gem->flags & EXYNOS_BO_NONCONTIG))
9940d9d93406f41 Marek Szyprowski 2020-04-23 43 attr |= DMA_ATTR_FORCE_CONTIGUOUS;
2a8cb4894540898 Joonyoung Shim 2015-08-16 44
2a8cb4894540898 Joonyoung Shim 2015-08-16 45 /*
2a8cb4894540898 Joonyoung Shim 2015-08-16 46 * if EXYNOS_BO_WC or EXYNOS_BO_NONCACHABLE, writecombine mapping
2a8cb4894540898 Joonyoung Shim 2015-08-16 47 * else cachable mapping.
2a8cb4894540898 Joonyoung Shim 2015-08-16 48 */
813fd67b57ffca0 Joonyoung Shim 2015-10-02 49 if (exynos_gem->flags & EXYNOS_BO_WC ||
813fd67b57ffca0 Joonyoung Shim 2015-10-02 50 !(exynos_gem->flags & EXYNOS_BO_CACHABLE))
9940d9d93406f41 Marek Szyprowski 2020-04-23 51 attr |= DMA_ATTR_WRITE_COMBINE;
2a8cb4894540898 Joonyoung Shim 2015-08-16 52
9940d9d93406f41 Marek Szyprowski 2020-04-23 53 /* FBDev emulation requires kernel mapping */
9940d9d93406f41 Marek Szyprowski 2020-04-23 54 if (!kvmap)
9940d9d93406f41 Marek Szyprowski 2020-04-23 55 attr |= DMA_ATTR_NO_KERNEL_MAPPING;
2a8cb4894540898 Joonyoung Shim 2015-08-16 56
9940d9d93406f41 Marek Szyprowski 2020-04-23 57 exynos_gem->dma_attrs = attr;
11e898373fba6b1 Chen-Yu Tsai 2026-03-26 58 exynos_gem->cookie = dma_alloc_attrs(drm_dev_dma_dev(dev), exynos_gem->base.size,
813fd67b57ffca0 Joonyoung Shim 2015-10-02 59 &exynos_gem->dma_addr, GFP_KERNEL,
00085f1efa387a8 Krzysztof Kozlowski 2016-08-03 60 exynos_gem->dma_attrs);
813fd67b57ffca0 Joonyoung Shim 2015-10-02 61 if (!exynos_gem->cookie) {
e457a1a9585b941 Chen-Yu Tsai 2026-03-26 62 DRM_DEV_ERROR(drm_dev_dma_dev(dev), "failed to allocate buffer.\n");
9940d9d93406f41 Marek Szyprowski 2020-04-23 63 return -ENOMEM;
2a8cb4894540898 Joonyoung Shim 2015-08-16 64 }
2a8cb4894540898 Joonyoung Shim 2015-08-16 65
9940d9d93406f41 Marek Szyprowski 2020-04-23 66 if (kvmap)
9940d9d93406f41 Marek Szyprowski 2020-04-23 67 exynos_gem->kvaddr = exynos_gem->cookie;
df547bf7735a623 Marek Szyprowski 2015-10-13 68
e457a1a9585b941 Chen-Yu Tsai 2026-03-26 @69 DRM_DEV_DEBUG_KMS(drm_dev_dma_dev(dev), "dma_addr(0x%lx), size(0x%lx)\n",
11e898373fba6b1 Chen-Yu Tsai 2026-03-26 70 (unsigned long)exynos_gem->dma_addr, exynos_gem->base.size);
2a8cb4894540898 Joonyoung Shim 2015-08-16 71 return 0;
2a8cb4894540898 Joonyoung Shim 2015-08-16 72 }
2a8cb4894540898 Joonyoung Shim 2015-08-16 73
:::::: The code at line 69 was first introduced by commit
:::::: e457a1a9585b941e2aa771142b63c951f6a3d54e drm/exynos: Use DRM core dedicated DMA device tracking facility
:::::: TO: Chen-Yu Tsai <wenst@chromium.org>
:::::: CC: Inki Dae <inki.dae@samsung.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-08 5:14 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=202604081331.jSJQSVmg-lkp@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wenst@chromium.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.