From: kernel test robot <lkp@intel.com>
To: Rafal Ostrowski <rafal.ostrowski@amd.com>
Cc: oe-kbuild-all@lists.linux.dev,
Alex Deucher <alexander.deucher@amd.com>,
Dillon Varone <dillon.varone@amd.com>,
Alex Hung <alex.hung@amd.com>
Subject: [agd5f:drm-next 41/71] Warning: drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c:71 expecting prototype for dc_assert_fp_enabled(). Prototype was for dc_is_fp_enabled() instead
Date: Wed, 01 Apr 2026 06:07:52 +0800 [thread overview]
Message-ID: <202604010622.OsEmKOCa-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/agd5f/linux.git drm-next
head: 8b3e8fa6d7bdab292447a43f70532db437d5d4f5
commit: 3539437f354bd24c98928a80d4db3a23fa2a7b19 [41/71] drm/amd/display: Move FPU Guards From DML To DC - Part 1
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260401/202604010622.OsEmKOCa-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260401/202604010622.OsEmKOCa-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/202604010622.OsEmKOCa-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c:71 expecting prototype for dc_assert_fp_enabled(). Prototype was for dc_is_fp_enabled() instead
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-31 22: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=202604010622.OsEmKOCa-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=dillon.varone@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafal.ostrowski@amd.com \
/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.