From: kernel test robot <lkp@intel.com>
To: Alex Deucher <alexander.deucher@amd.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [agd5f:kq_resets 7/28] drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:774: warning: Function parameter or struct member 'seq' not described in 'amdgpu_fence_driver_seq_force_completion'
Date: Mon, 2 Jun 2025 03:08:21 +0800 [thread overview]
Message-ID: <202506020336.FFIzr004-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/agd5f/linux.git kq_resets
head: 0cb5804810f5e8aef9503d3d50c98a02a26f9216
commit: 5a61fa3e46a6b799d013c560d2b90d4e8b78cbbb [7/28] drm/amdgpu: track ring state associated with a job
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250602/202506020336.FFIzr004-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250602/202506020336.FFIzr004-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/202506020336.FFIzr004-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:774: warning: Function parameter or struct member 'seq' not described in 'amdgpu_fence_driver_seq_force_completion'
vim +774 drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
766
767 /**
768 * amdgpu_fence_driver_seq_force_completion - force signal of specified sequence
769 *
770 * @ring: fence of the ring to signal
771 *
772 */
773 void amdgpu_fence_driver_seq_force_completion(struct amdgpu_ring *ring, u32 seq)
> 774 {
775 amdgpu_fence_write(ring, seq);
776 amdgpu_fence_process(ring);
777 }
778
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-06-01 19:08 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=202506020336.FFIzr004-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.deucher@amd.com \
--cc=llvm@lists.linux.dev \
--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