From: kernel test robot <yujie.liu@intel.com>
To: Harry Wentland <harry.wentland@amd.com>
Cc: <kbuild-all@lists.01.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Alex Deucher <alexander.deucher@amd.com>
Subject: [linux-next:master 7600/8197] drivers/gpu/drm/amd/display/dc/os_types.h: drm/drm_print.h is included more than once.
Date: Thu, 7 Jul 2022 14:36:47 +0800 [thread overview]
Message-ID: <c6a3cf19-dfd3-7519-0939-6b6a44f42315@intel.com> (raw)
In-Reply-To: <202207070341.YLD8BfwB-lkp@intel.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 088b9c375534d905a4d337c78db3b3bfbb52c4a0
commit: 09de5cd2c170b19e04e37439a712da52a0535015 [7600/8197] drm/amd/display: Move all linux includes into OS types
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <yujie.liu@intel.com>
includecheck warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/amd/display/dc/os_types.h: drm/drm_print.h is included more than once.
4fc4dca8320e4 (Sam Ravnborg 2019-06-10 00:07:50 +0200 37) #include <asm/byteorder.h>
4fc4dca8320e4 (Sam Ravnborg 2019-06-10 00:07:50 +0200 38)
da68386d9edb1 (Thomas Zimmermann 2022-04-21 09:31:02 +0200 39) #include <drm/display/drm_dp_helper.h>
4fc4dca8320e4 (Sam Ravnborg 2019-06-10 00:07:50 +0200 @40) #include <drm/drm_print.h>
93052132568ae (Dave Airlie 2017-10-03 12:38:57 +1000 41)
09de5cd2c170b (Harry Wentland 2019-11-22 10:12:51 -0500 @42) #include <drm/drm_print.h>
09de5cd2c170b (Harry Wentland 2019-11-22 10:12:51 -0500 43)
160b8e75932fd (Rex Zhu 2018-03-20 19:19:44 +0800 44) #include "cgs_common.h"
--
0-DAY CI Kernel Test Service
https://01.org/lkp
parent reply other threads:[~2022-07-07 6:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <202207070341.YLD8BfwB-lkp@intel.com>]
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=c6a3cf19-dfd3-7519-0939-6b6a44f42315@intel.com \
--to=yujie.liu@intel.com \
--cc=alexander.deucher@amd.com \
--cc=harry.wentland@amd.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
/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