From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [drm-xe:drm-xe-next 1/2] drivers/gpu/drm/xe/xe_gt.c: generated/xe_wa_oob.h is included more than once.
Date: Fri, 5 Jul 2024 21:40:59 +0800 [thread overview]
Message-ID: <202407052122.AzuWSPuo-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: intel-xe@lists.freedesktop.org
TO: Matthew Auld <matthew.auld@intel.com>
CC: Jonathan Cavitt <jonathan.cavitt@intel.com>
tree: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
head: c55f79f317ab428ae6d005965bc07e37496f209f
commit: 01570b446939c3538b1aa3d059837f49fa14a3ae [1/2] drm/xe/bmg: implement Wa_16023588340
:::::: branch date: 5 hours ago
:::::: commit date: 5 hours ago
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
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/202407052122.AzuWSPuo-lkp@intel.com/
includecheck warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/xe/xe_gt.c: generated/xe_wa_oob.h is included more than once.
vim +12 drivers/gpu/drm/xe/xe_gt.c
9
10 #include <drm/drm_managed.h>
11 #include <drm/xe_drm.h>
> 12 #include <generated/xe_wa_oob.h>
13
> 14 #include <generated/xe_wa_oob.h>
15
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-07-05 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 13:40 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-05 14:30 [drm-xe:drm-xe-next 1/2] drivers/gpu/drm/xe/xe_gt.c: generated/xe_wa_oob.h is included more than once kernel test robot
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=202407052122.AzuWSPuo-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 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.