From: kernel test robot <lkp@intel.com>
To: Dominik Kaszewski <dominik.kaszewski@amd.com>
Cc: oe-kbuild-all@lists.linux.dev,
Alex Deucher <alexander.deucher@amd.com>,
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>,
Chenyu Chen <chen-yu.chen@amd.com>,
linux-doc@vger.kernel.org
Subject: [drm-amdgpu:drm-amdgpu-next 47/114] Warning: drivers/gpu/drm/amd/amdgpu/../display/dc/dc_memory_pool.c:1 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
Date: Wed, 23 Sep 2026 10:43:58 +0200 [thread overview]
Message-ID: <202609231020.wPkQLbDG-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/drm/amdgpu/kernel drm-amdgpu-next
head: cf48bd0a46279f4607956cb17c71bda96ee802e3
commit: 6f74688d7e2377e253671d36acd63a988186216b [47/114] drm/amd/display: Add lock-free memory pool
config: riscv-randconfig-2001-20260923 (https://download.01.org/0day-ci/archive/20260923/202609231020.wPkQLbDG-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260923/202609231020.wPkQLbDG-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/202609231020.wPkQLbDG-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/gpu/drm/amd/amdgpu/../display/dc/dc_memory_pool.c:1 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
* Copyright (C) Advanced Micro Devices, Inc. All rights reserved.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-23 8:44 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=202609231020.wPkQLbDG-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.deucher@amd.com \
--cc=chen-yu.chen@amd.com \
--cc=dominik.kaszewski@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=nicholas.kazlauskas@amd.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