From: kernel test robot <lkp@intel.com>
To: Christian =?unknown-8bit?B?S8O2bmln?=
<ckoenig.leichtzumerken@gmail.com>,
kraxel@redhat.com, airlied@redhat.com, alexander.deucher@amd.com,
zack.rusin@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
virtualization@lists.linux.dev, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 4/7] drm/vmwgfx: use the new drm_exec object
Date: Sun, 17 Nov 2024 17:15:49 +0800 [thread overview]
Message-ID: <202411171611.9LEZwWSe-lkp@intel.com> (raw)
In-Reply-To: <20241114153020.6209-5-christian.koenig@amd.com>
Hi Christian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on drm/drm-next drm-exynos/exynos-drm-next linus/master drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip v6.12-rc7 next-20241115]
[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/Christian-K-nig/drm-qxl-switch-to-using-drm_exec-v2/20241115-014610
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link: https://lore.kernel.org/r/20241114153020.6209-5-christian.koenig%40amd.com
patch subject: [PATCH 4/7] drm/vmwgfx: use the new drm_exec object
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20241117/202411171611.9LEZwWSe-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241117/202411171611.9LEZwWSe-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/202411171611.9LEZwWSe-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/vmwgfx/vmwgfx_validation.c:861: warning: Function parameter or struct member 'fence' not described in 'vmw_validation_bo_fence'
vim +861 drivers/gpu/drm/vmwgfx/vmwgfx_validation.c
850
851 /**
852 * vmw_validation_bo_fence - Unreserve and fence buffer objects registered
853 * with a validation context
854 * @ctx: The validation context
855 *
856 * This function unreserves the buffer objects previously reserved using
857 * vmw_validation_bo_reserve, and fences them with a fence object.
858 */
859 void vmw_validation_bo_fence(struct vmw_validation_context *ctx,
860 struct vmw_fence_obj *fence)
> 861 {
862 struct vmw_validation_bo_node *entry;
863
864 list_for_each_entry(entry, &ctx->bo_list, base.head) {
865 dma_resv_add_fence(entry->base.bo->base.resv, &fence->base,
866 DMA_RESV_USAGE_READ);
867 }
868 drm_exec_fini(&ctx->exec);
869 }
870
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-17 9:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 15:30 Switch remaining drivers over to drm_exec Christian König
2024-11-14 15:30 ` [PATCH 1/7] drm/radeon: switch over to drm_exec v2 Christian König
2024-11-14 20:50 ` Alex Deucher
2024-11-14 15:30 ` [PATCH 2/7] drm/qxl: switch to using " Christian König
2024-11-14 20:53 ` Alex Deucher
2024-11-14 15:30 ` [PATCH 3/7] drm/vmwgfx: start to phase out ttm_exec Christian König
2024-11-17 7:12 ` kernel test robot
2024-11-14 15:30 ` [PATCH 4/7] drm/vmwgfx: use the new drm_exec object Christian König
2024-11-17 9:15 ` kernel test robot [this message]
2024-11-14 15:30 ` [PATCH 5/7] drm/vmwgfx: replace ttm_validate_buffer with separate struct Christian König
2024-11-14 15:30 ` [PATCH 6/7] drm/xe: drop unused component dependencies Christian König
2024-11-14 17:31 ` Lucas De Marchi
2024-11-14 15:30 ` [PATCH 7/7] drm/ttm: remove ttm_execbug_util Christian König
2024-11-14 16:47 ` ✓ CI.Patch_applied: success for series starting with [1/7] drm/radeon: switch over to drm_exec v2 Patchwork
2024-11-14 16:48 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-14 16:50 ` ✓ CI.KUnit: success " Patchwork
2024-11-14 17:06 ` ✓ CI.Build: " Patchwork
2024-11-14 17:08 ` ✓ CI.Hooks: " Patchwork
2024-11-14 17:10 ` ✗ CI.checksparse: warning " Patchwork
2024-11-14 17:36 ` ✓ CI.BAT: success " Patchwork
2024-11-15 9:53 ` ✗ CI.FULL: failure " Patchwork
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=202411171611.9LEZwWSe-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
--cc=zack.rusin@broadcom.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