From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [agd5f:amd-staging-drm-next 2021/2033] drivers/gpu/drm/amd/display/dc/inc/hw/transform.h: spl/dc_spl_types.h is included more than once.
Date: Thu, 25 Apr 2024 12:03:55 +0800 [thread overview]
Message-ID: <202404251153.Ed5aHK5H-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Aurabindo Pillai <aurabindo.pillai@amd.com>
tree: https://gitlab.freedesktop.org/agd5f/linux.git amd-staging-drm-next
head: 5550c5defbdf958f2df459be74f87afa9eb0bdde
commit: 4331f4f5985cec71a0ca058d8e58d77016e1498e [2021/2033] drm/amd/display: Add misc DC changes for DCN401
:::::: branch date: 2 days ago
:::::: commit date: 3 days ago
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
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/r/202404251153.Ed5aHK5H-lkp@intel.com/
includecheck warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/amd/display/dc/inc/hw/transform.h: spl/dc_spl_types.h is included more than once.
vim +32 drivers/gpu/drm/amd/display/dc/inc/hw/transform.h
28
29 #include "hw_shared.h"
30 #include "dc_hw_types.h"
31 #include "fixed31_32.h"
> 32 #include "spl/dc_spl_types.h"
33
> 34 #include "spl/dc_spl_types.h"
35
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-25 4:04 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=202404251153.Ed5aHK5H-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).