From: kernel test robot <lkp@intel.com>
To: dongwon.kim@intel.com, dri-devel@lists.freedesktop.org,
airlied@redhat.com, kraxel@redhat.com,
dmitry.osipenko@collabora.com
Cc: oe-kbuild-all@lists.linux.dev, nirmoyd@nvidia.com,
vivek.kasireddy@intel.com
Subject: Re: [PATCH v7 2/3] drm/virtio: Add support for saving and restoring virtio_gpu_objects
Date: Mon, 12 Jan 2026 16:16:36 +0800 [thread overview]
Message-ID: <202601121246.Q3BHNIsw-lkp@intel.com> (raw)
In-Reply-To: <20260107182745.229481-3-dongwon.kim@intel.com>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm/drm-next daeinki-drm-exynos/exynos-drm-next drm-i915/for-linux-next drm-i915/for-linux-next-fixes drm-tip/drm-tip linus/master v6.19-rc4 next-20260109]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/dongwon-kim-intel-com/drm-virtio-Freeze-and-restore-hooks-to-support-suspend-and-resume/20260108-024124
base: https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next
patch link: https://lore.kernel.org/r/20260107182745.229481-3-dongwon.kim%40intel.com
patch subject: [PATCH v7 2/3] drm/virtio: Add support for saving and restoring virtio_gpu_objects
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20260112/202601121246.Q3BHNIsw-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260112/202601121246.Q3BHNIsw-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/202601121246.Q3BHNIsw-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/virtio/virtgpu_prime.c: In function 'virtgpu_dma_buf_obj_resubmit':
>> drivers/gpu/drm/virtio/virtgpu_prime.c:291:17: error: implicit declaration of function 'DRM_ERROR'; did you mean 'DRM_IOR'? [-Wimplicit-function-declaration]
291 | DRM_ERROR("no sgt bound to virtio_gpu_object\n");
| ^~~~~~~~~
| DRM_IOR
vim +291 drivers/gpu/drm/virtio/virtgpu_prime.c
282
283 int virtgpu_dma_buf_obj_resubmit(struct virtio_gpu_device *vgdev,
284 struct virtio_gpu_object *bo)
285 {
286 struct virtio_gpu_mem_entry *ents;
287 struct scatterlist *sl;
288 int i;
289
290 if (!bo->sgt) {
> 291 DRM_ERROR("no sgt bound to virtio_gpu_object\n");
292 return -ENOMEM;
293 }
294
295 ents = kvmalloc_array(bo->sgt->nents,
296 sizeof(struct virtio_gpu_mem_entry),
297 GFP_KERNEL);
298 if (!ents) {
299 DRM_ERROR("failed to allocate ent list\n");
300 return -ENOMEM;
301 }
302
303 for_each_sgtable_dma_sg(bo->sgt, sl, i) {
304 ents[i].addr = cpu_to_le64(sg_dma_address(sl));
305 ents[i].length = cpu_to_le32(sg_dma_len(sl));
306 ents[i].padding = 0;
307 }
308
309 virtio_gpu_cmd_resource_create_blob(vgdev, bo, &bo->params,
310 ents, bo->sgt->nents);
311
312 return 0;
313 }
314
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-12 8:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 18:27 [PATCH v7 0/3] Virtio-GPU S4 support dongwon.kim
2026-01-07 18:27 ` [PATCH v7 1/3] drm/virtio: Freeze and restore hooks to support suspend and resume dongwon.kim
2026-02-25 16:06 ` Dmitry Osipenko
2026-01-07 18:27 ` [PATCH v7 2/3] drm/virtio: Add support for saving and restoring virtio_gpu_objects dongwon.kim
2026-01-09 16:40 ` kernel test robot
2026-01-12 4:03 ` kernel test robot
2026-01-12 8:16 ` kernel test robot [this message]
2026-02-25 16:07 ` Dmitry Osipenko
2026-01-07 18:27 ` [PATCH v7 3/3] drm/virtio: Add PM notifier to restore objects after hibernation dongwon.kim
2026-02-25 16:06 ` Dmitry Osipenko
2026-02-25 16:06 ` Dmitry Osipenko
2026-02-25 16:05 ` [PATCH v7 0/3] Virtio-GPU S4 support Dmitry Osipenko
2026-02-25 17:06 ` Kim, Dongwon
2026-04-30 22:39 ` Dmitry Osipenko
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=202601121246.Q3BHNIsw-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@redhat.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dongwon.kim@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=nirmoyd@nvidia.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vivek.kasireddy@intel.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