From: kernel test robot <lkp@intel.com>
To: Luben Tuikov <ltuikov89@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>
Subject: [drm-misc:for-linux-next 2/3] drivers/gpu/drm/nouveau/nouveau_sched.c:21:34: error: use of undeclared identifier 'DRM_SCHED_PRIORITY_MIN'
Date: Sat, 25 Nov 2023 23:00:30 +0800 [thread overview]
Message-ID: <202311252109.WgbJsSkG-lkp@intel.com> (raw)
Hi Luben,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: git://anongit.freedesktop.org/drm/drm-misc for-linux-next
head: 38f922a563aac3148ac73e73689805917f034cb5
commit: fe375c74806dbd30b00ec038a80a5b7bf4653ab7 [2/3] drm/sched: Rename priority MIN to LOW
config: x86_64-randconfig-123-20231125 (https://download.01.org/0day-ci/archive/20231125/202311252109.WgbJsSkG-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231125/202311252109.WgbJsSkG-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/202311252109.WgbJsSkG-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/nouveau/nouveau_sched.c:21:34: error: use of undeclared identifier 'DRM_SCHED_PRIORITY_MIN'
NOUVEAU_SCHED_PRIORITY_SINGLE = DRM_SCHED_PRIORITY_MIN,
^
drivers/gpu/drm/nouveau/nouveau_sched.c:436:38: error: use of undeclared identifier 'DRM_SCHED_PRIORITY_MIN'
ret = drm_sched_entity_init(entity, DRM_SCHED_PRIORITY_MIN,
^
2 errors generated.
vim +/DRM_SCHED_PRIORITY_MIN +21 drivers/gpu/drm/nouveau/nouveau_sched.c
b88baab828713c Danilo Krummrich 2023-08-04 16
5f03a507b29e44 Danilo Krummrich 2023-11-14 17 /* Starts at 0, since the DRM scheduler interprets those parameters as (initial)
5f03a507b29e44 Danilo Krummrich 2023-11-14 18 * index to the run-queue array.
5f03a507b29e44 Danilo Krummrich 2023-11-14 19 */
5f03a507b29e44 Danilo Krummrich 2023-11-14 20 enum nouveau_sched_priority {
5f03a507b29e44 Danilo Krummrich 2023-11-14 @21 NOUVEAU_SCHED_PRIORITY_SINGLE = DRM_SCHED_PRIORITY_MIN,
5f03a507b29e44 Danilo Krummrich 2023-11-14 22 NOUVEAU_SCHED_PRIORITY_COUNT,
5f03a507b29e44 Danilo Krummrich 2023-11-14 23 };
5f03a507b29e44 Danilo Krummrich 2023-11-14 24
:::::: The code at line 21 was first introduced by commit
:::::: 5f03a507b29e44a848f315c7240c19894dd8be4f drm/nouveau: implement 1:1 scheduler - entity relationship
:::::: TO: Danilo Krummrich <dakr@redhat.com>
:::::: CC: Danilo Krummrich <dakr@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-25 15:01 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=202311252109.WgbJsSkG-lkp@intel.com \
--to=lkp@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ltuikov89@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).