From: kernel test robot <lkp@intel.com>
To: Melissa Wen <mwen@igalia.com>,
airlied@gmail.com, alexander.deucher@amd.com,
christian.koenig@amd.com, harry.wentland@amd.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
simona@ffwll.ch, siqueira@igalia.com, sunpeng.li@amd.com,
tzimmermann@suse.de
Cc: oe-kbuild-all@lists.linux.dev, Alex Hung <alex.hung@amd.com>,
Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>,
Simon Ser <contact@emersion.fr>,
Uma Shankar <uma.shankar@intel.com>,
Xaver Hugl <xaver.hugl@kde.org>,
amd-gfx@lists.freedesktop.org, kernel-dev@igalia.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/atomic: track individual colorop updates
Date: Thu, 19 Mar 2026 17:16:08 +0800 [thread overview]
Message-ID: <202603191755.nmfoAOS4-lkp@intel.com> (raw)
In-Reply-To: <20260318162348.299807-2-mwen@igalia.com>
Hi Melissa,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on linus/master v7.0-rc4 next-20260318]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Melissa-Wen/drm-atomic-track-individual-colorop-updates/20260319-023607
base: https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next
patch link: https://lore.kernel.org/r/20260318162348.299807-2-mwen%40igalia.com
patch subject: [PATCH 1/2] drm/atomic: track individual colorop updates
config: arc-randconfig-002-20260319 (https://download.01.org/0day-ci/archive/20260319/202603191755.nmfoAOS4-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260319/202603191755.nmfoAOS4-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/202603191755.nmfoAOS4-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/msm/msm_atomic.c:7:
>> include/drm/drm_atomic_uapi.h:53:1: error: unknown type name 'bool'
53 | bool drm_atomic_set_colorop_for_plane(struct drm_plane_state *plane_state,
| ^~~~
include/drm/drm_atomic_uapi.h:1:1: note: 'bool' is defined in header '<stdbool.h>'; did you forget to '#include <stdbool.h>'?
+++ |+#include <stdbool.h>
1 | /*
vim +/bool +53 include/drm/drm_atomic_uapi.h
41
42 int __must_check
43 drm_atomic_set_mode_for_crtc(struct drm_crtc_state *state,
44 const struct drm_display_mode *mode);
45 int __must_check
46 drm_atomic_set_mode_prop_for_crtc(struct drm_crtc_state *state,
47 struct drm_property_blob *blob);
48 int __must_check
49 drm_atomic_set_crtc_for_plane(struct drm_plane_state *plane_state,
50 struct drm_crtc *crtc);
51 void drm_atomic_set_fb_for_plane(struct drm_plane_state *plane_state,
52 struct drm_framebuffer *fb);
> 53 bool drm_atomic_set_colorop_for_plane(struct drm_plane_state *plane_state,
54 struct drm_colorop *colorop);
55 int __must_check
56 drm_atomic_set_crtc_for_connector(struct drm_connector_state *conn_state,
57 struct drm_crtc *crtc);
58
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-19 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 16:12 [PATCH 0/2] drm/atomic: track colorop changes of a given plane Melissa Wen
2026-03-18 16:12 ` [PATCH 1/2] drm/atomic: track individual colorop updates Melissa Wen
2026-03-18 17:58 ` Harry Wentland
2026-03-19 9:16 ` kernel test robot [this message]
2026-03-18 16:12 ` [PATCH 2/2] drm/amd/display: use plane color_mgmt_changed to track colorop changes Melissa Wen
2026-03-18 17:59 ` Harry Wentland
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=202603191755.nmfoAOS4-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=chaitanya.kumar.borah@intel.com \
--cc=christian.koenig@amd.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=kernel-dev@igalia.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=mwen@igalia.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.com \
--cc=tzimmermann@suse.de \
--cc=uma.shankar@intel.com \
--cc=xaver.hugl@kde.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