From: kernel test robot <lkp@intel.com>
To: Philip Yang <Philip.Yang@amd.com>
Cc: <llvm@lists.linux.dev>, <oe-kbuild-all@lists.linux.dev>,
Alex Deucher <alexander.deucher@amd.com>,
Felix Kuehling <felix.kuehling@amd.com>
Subject: [agd5f:ualink 119/183] Warning: drivers/gpu/drm/amd/amdgpu/amdgpu_ualink.c:1508 expecting prototype for amdgpu_npa_vm_unmap_range(). Prototype was for amdgpu_ualink_npa_vm_unmap_range() instead
Date: Sun, 23 Aug 2026 19:44:44 +0800 [thread overview]
Message-ID: <202608231508.UL0l4d1j-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/agd5f/linux.git ualink
head: 67bd1d6d1b25ea1f893a76fffd13dd6335d297d0
commit: a99387aaf204a69b6f88f80c858cc17a0943b0d6 [119/183] drm/amdgpu: Add UALink NPA VM mapping for ring buffers
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20260823/202608231508.UL0l4d1j-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 935bfc708590c60147a79c7df145bb6e68b1d388)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260823/202608231508.UL0l4d1j-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/202608231508.UL0l4d1j-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/gpu/drm/amd/amdgpu/amdgpu_ualink.c:1508 expecting prototype for amdgpu_npa_vm_unmap_range(). Prototype was for amdgpu_ualink_npa_vm_unmap_range() instead
Warning: drivers/gpu/drm/amd/amdgpu/amdgpu_ualink.c:1598 bad line:
Warning: drivers/gpu/drm/amd/amdgpu/amdgpu_ualink.c:1605 expecting prototype for amdgpu_ualink_gart_npa_addr(). Prototype was for AMDGPU_UALINK_GART_NPA_ADDR_GPUID_SHIFT() instead
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-23 11: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=202608231508.UL0l4d1j-lkp@intel.com \
--to=lkp@intel.com \
--cc=Philip.Yang@amd.com \
--cc=alexander.deucher@amd.com \
--cc=felix.kuehling@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