From: kernel test robot <lkp@intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
thomas_os@shipmail.org, boris.brezillon@collabora.com,
arunpravin.paneerselvam@amd.com, dakr@redhat.com,
dri-devel@lists.freedesktop.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 2/2] drm: add drm_exec selftests v4
Date: Thu, 22 Jun 2023 00:27:26 +0800 [thread overview]
Message-ID: <202306220013.JRZDDrkO-lkp@intel.com> (raw)
In-Reply-To: <20230621133700.7588-2-christian.koenig@amd.com>
Hi Christian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm/drm-next drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.4-rc7 next-20230621]
[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-v4/20230621-213827
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20230621133700.7588-2-christian.koenig%40amd.com
patch subject: [PATCH 2/2] drm: add drm_exec selftests v4
config: hexagon-randconfig-r015-20230621 (https://download.01.org/0day-ci/archive/20230622/202306220013.JRZDDrkO-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20230622/202306220013.JRZDDrkO-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/202306220013.JRZDDrkO-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/tests/drm_exec_test.c:134:2: warning: variable '__drm_exec_retry_ptr' set but not used [-Wunused-but-set-variable]
134 | drm_exec_until_all_locked(&exec)
| ^
include/drm/drm_exec.h:78:13: note: expanded from macro 'drm_exec_until_all_locked'
78 | for (void *__drm_exec_retry_ptr; ({ \
| ^
1 warning generated.
vim +/__drm_exec_retry_ptr +134 drivers/gpu/drm/tests/drm_exec_test.c
121
122 static void test_prepare_array(struct kunit *test)
123 {
124 struct drm_gem_object gobj1 = { };
125 struct drm_gem_object gobj2 = { };
126 struct drm_gem_object *array[] = { &gobj1, &gobj2 };
127 struct drm_exec exec;
128 int ret;
129
130 drm_gem_private_object_init(&dev, &gobj1, PAGE_SIZE);
131 drm_gem_private_object_init(&dev, &gobj2, PAGE_SIZE);
132
133 drm_exec_init(&exec, DRM_EXEC_INTERRUPTIBLE_WAIT);
> 134 drm_exec_until_all_locked(&exec)
135 ret = drm_exec_prepare_array(&exec, array, ARRAY_SIZE(array),
136 1);
137 KUNIT_EXPECT_EQ(test, ret, 0);
138 drm_exec_fini(&exec);
139 }
140
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-06-21 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 13:36 [PATCH 1/2] drm: execution context for GEM buffers v5 Christian König
2023-06-21 13:37 ` [PATCH 2/2] drm: add drm_exec selftests v4 Christian König
2023-06-21 16:27 ` kernel test robot [this message]
2023-06-21 16:48 ` kernel test robot
2023-06-21 16:48 ` kernel test robot
2023-06-21 14:01 ` [PATCH 1/2] drm: execution context for GEM buffers v5 Thomas Hellström (Intel)
2023-06-21 14:08 ` Boris Brezillon
2023-06-21 16:51 ` Boris Brezillon
2023-06-21 16:54 ` Boris Brezillon
2023-06-22 16:10 ` 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=202306220013.JRZDDrkO-lkp@intel.com \
--to=lkp@intel.com \
--cc=arunpravin.paneerselvam@amd.com \
--cc=boris.brezillon@collabora.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dakr@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas_os@shipmail.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.