From: kernel test robot <lkp@intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: arunpravin.paneerselvam@amd.com, dakr@redhat.com,
oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 8/9] drm/qxl: switch to using drm_exec
Date: Wed, 1 Mar 2023 00:03:57 +0800 [thread overview]
Message-ID: <202302282339.welAynWc-lkp@intel.com> (raw)
In-Reply-To: <20230228083406.1720795-9-christian.koenig@amd.com>
Hi Christian,
I love your patch! Yet something to improve:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm/drm-next drm-intel/for-linux-next linus/master next-20230228]
[cannot apply to drm-exynos/exynos-drm-next drm-intel/for-linux-next-fixes v6.2]
[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-add-drm_exec-selftests/20230228-173404
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20230228083406.1720795-9-christian.koenig%40amd.com
patch subject: [PATCH 8/9] drm/qxl: switch to using drm_exec
config: i386-randconfig-a014-20230227 (https://download.01.org/0day-ci/archive/20230228/202302282339.welAynWc-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/435d2421797eb683d27984c9a823b48704069df9
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Christian-K-nig/drm-add-drm_exec-selftests/20230228-173404
git checkout 435d2421797eb683d27984c9a823b48704069df9
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 olddefconfig
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202302282339.welAynWc-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "drm_exec_init" [drivers/gpu/drm/qxl/qxl.ko] undefined!
>> ERROR: modpost: "drm_exec_prepare_obj" [drivers/gpu/drm/qxl/qxl.ko] undefined!
>> ERROR: modpost: "drm_exec_cleanup" [drivers/gpu/drm/qxl/qxl.ko] undefined!
>> ERROR: modpost: "drm_exec_fini" [drivers/gpu/drm/qxl/qxl.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-02-28 16:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 8:33 Common DRM execution context v3 Christian König
2023-02-28 8:33 ` [PATCH 1/9] drm: execution context for GEM buffers v3 Christian König
2023-02-28 19:13 ` Danilo Krummrich
2023-03-02 7:49 ` Christian König
2023-03-03 13:45 ` Luben Tuikov
2023-03-03 14:11 ` Luben Tuikov
2023-03-10 10:42 ` Thomas Hellström (Intel)
2023-04-14 14:29 ` Francois Dugast
2023-02-28 8:33 ` [PATCH 2/9] drm: add drm_exec selftests Christian König
2023-02-28 8:34 ` [PATCH 3/9] drm/amdkfd: switch over to using drm_exec Christian König
2023-04-21 21:28 ` Felix Kuehling
2023-02-28 8:34 ` [PATCH 4/9] drm/amdgpu: use drm_exec for GEM and CSA handling Christian König
2023-02-28 8:34 ` [PATCH 5/9] drm/amdgpu: use drm_exec for MES testing Christian König
2023-02-28 8:34 ` [PATCH 6/9] drm/amdgpu: use the new drm_exec object for CS v2 Christian König
2023-02-28 8:34 ` [PATCH 7/9] drm/radeon: switch over to drm_exec Christian König
2023-02-28 16:45 ` kernel test robot
2023-02-28 8:34 ` [PATCH 8/9] drm/qxl: switch to using drm_exec Christian König
2023-02-28 16:03 ` kernel test robot [this message]
2023-02-28 16:34 ` kernel test robot
2023-02-28 8:34 ` [PATCH 9/9] drm: move ttm_execbuf_util into vmwgfx Christian König
2023-03-08 5:14 ` Zack Rusin
2023-03-08 9:10 ` Christian König
2023-03-09 5:14 ` Zack Rusin
2023-03-09 8:35 ` Thomas Hellström (Intel)
2023-03-09 8:26 ` Thomas Hellström (Intel)
2023-02-28 19:11 ` Common DRM execution context v3 Danilo Krummrich
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=202302282339.welAynWc-lkp@intel.com \
--to=lkp@intel.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arunpravin.paneerselvam@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dakr@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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