[agd5f:kq_resets 12/35] drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:740: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst

[agd5f:kq_resets 12/35] drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:740: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst

[kernel test robot]

tree:   https://gitlab.freedesktop.org/agd5f/linux.git kq_resets
head:   913a6a46f5130fdd3baf24bc4425c81ac238070f
commit: 897a07925f1b164d513618042dcfcfdfaab43e4d [12/35] drm/amdgpu: track ring state associated with a fence
config: sparc64-randconfig-001-20250620 (https://download.01.org/0day-ci/archive/20250621/202506210401.54n8AMH4-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250621/202506210401.54n8AMH4-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/202506210401.54n8AMH4-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:740: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Kernel queue reset handling


vim +740 drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c

   737	
   738	
   739	/**
 > 740	 * Kernel queue reset handling
   741	 *
   742	 * The driver can reset individual queues for most engines, but those queues
   743	 * may contain work from multiple contexts.  Resetting the queue will reset
   744	 * lose all of that state.  In order to minimize the collatoral damage, the
   745	 * driver will save the ring contents which are not associated with the guilty
   746	 * context prior to resetting the queue.  After resetting the queue the queue
   747	 * contents from the other contexts is re-emitted to the rings so that it can
   748	 * be processed by the engine.  To handle this, we save the queue's write
   749	 * pointer (wptr) in the fences associated with each context.  If we get a
   750	 * queue timeout, we can then use the wptrs from the fences to determine
   751	 * which data needs to be saved out of the queue's ring buffer.
   752	 */
   753	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki