From: kernel test robot <lkp@intel.com>
To: Albert Esteve <aesteve@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
George Zhang <george.zhang@amd.com>
Subject: [agd5f:tlb_inv_rework 3282/3548] ERROR: modpost: drivers/gpu/drm/amd/amdgpu/amdgpu: local symbol 'amdgpu_dm_atomic_check' was exported
Date: Thu, 08 Oct 2026 07:31:52 +0800 [thread overview]
Message-ID: <202610080733.Ds7Eax7S-lkp@intel.com> (raw)
Hi Albert,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://gitlab.freedesktop.org/agd5f/linux.git tlb_inv_rework
head: 3bf3b4ea31b252534f7038ab792f333801366586
commit: b235c73f94782c252119bc8cfc2a21ffad72d338 [3282/3548] drm/amd/display: replace EXPORT_IF_KUNIT with EXPORT_SYMBOL_IF_KUNIT
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20261008/202610080733.Ds7Eax7S-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261008/202610080733.Ds7Eax7S-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/202610080733.Ds7Eax7S-lkp@intel.com/
Note: the agd5f/tlb_inv_rework HEAD 3bf3b4ea31b252534f7038ab792f333801366586 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: drivers/gpu/drm/amd/amdgpu/amdgpu: local symbol 'amdgpu_dm_atomic_check' was exported
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-07 23:32 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=202610080733.Ds7Eax7S-lkp@intel.com \
--to=lkp@intel.com \
--cc=aesteve@redhat.com \
--cc=george.zhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.