From: kernel test robot <lkp@intel.com>
To: Jessica Zhang <quic_jesszhan@quicinc.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] drm/msm/dpu: Support YUV formats on writeback for DPU 5.x+
Date: Fri, 7 Mar 2025 20:30:52 +0800 [thread overview]
Message-ID: <202503072004.KTOFOoOq-lkp@intel.com> (raw)
In-Reply-To: <20250305-cdm-yuv-fix-v1-1-5f1dd8ecf76c@quicinc.com>
Hi Jessica,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 6d3175a72cc07e90f81fb35841048a8a9b5134cb]
url: https://github.com/intel-lab-lkp/linux/commits/Jessica-Zhang/drm-msm-dpu-Support-YUV-formats-on-writeback-for-DPU-5-x/20250306-111647
base: 6d3175a72cc07e90f81fb35841048a8a9b5134cb
patch link: https://lore.kernel.org/r/20250305-cdm-yuv-fix-v1-1-5f1dd8ecf76c%40quicinc.com
patch subject: [PATCH] drm/msm/dpu: Support YUV formats on writeback for DPU 5.x+
config: loongarch-allyesconfig (https://download.01.org/0day-ci/archive/20250307/202503072004.KTOFOoOq-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250307/202503072004.KTOFOoOq-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/202503072004.KTOFOoOq-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c:235:18: warning: 'wb2_formats_rgb' defined but not used [-Wunused-const-variable=]
235 | static const u32 wb2_formats_rgb[] = {
| ^~~~~~~~~~~~~~~
vim +/wb2_formats_rgb +235 drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c
dabfdd89eaa928 Vinod Polimera 2022-04-11 234
8c16b988ba2d3d Abhinav Kumar 2023-12-12 @235 static const u32 wb2_formats_rgb[] = {
53324b99bd7b4d Abhinav Kumar 2022-04-26 236 DRM_FORMAT_RGB565,
53324b99bd7b4d Abhinav Kumar 2022-04-26 237 DRM_FORMAT_BGR565,
53324b99bd7b4d Abhinav Kumar 2022-04-26 238 DRM_FORMAT_RGB888,
53324b99bd7b4d Abhinav Kumar 2022-04-26 239 DRM_FORMAT_ARGB8888,
53324b99bd7b4d Abhinav Kumar 2022-04-26 240 DRM_FORMAT_RGBA8888,
53324b99bd7b4d Abhinav Kumar 2022-04-26 241 DRM_FORMAT_ABGR8888,
53324b99bd7b4d Abhinav Kumar 2022-04-26 242 DRM_FORMAT_XRGB8888,
53324b99bd7b4d Abhinav Kumar 2022-04-26 243 DRM_FORMAT_RGBX8888,
53324b99bd7b4d Abhinav Kumar 2022-04-26 244 DRM_FORMAT_XBGR8888,
53324b99bd7b4d Abhinav Kumar 2022-04-26 245 DRM_FORMAT_ARGB1555,
53324b99bd7b4d Abhinav Kumar 2022-04-26 246 DRM_FORMAT_RGBA5551,
53324b99bd7b4d Abhinav Kumar 2022-04-26 247 DRM_FORMAT_XRGB1555,
53324b99bd7b4d Abhinav Kumar 2022-04-26 248 DRM_FORMAT_RGBX5551,
53324b99bd7b4d Abhinav Kumar 2022-04-26 249 DRM_FORMAT_ARGB4444,
53324b99bd7b4d Abhinav Kumar 2022-04-26 250 DRM_FORMAT_RGBA4444,
53324b99bd7b4d Abhinav Kumar 2022-04-26 251 DRM_FORMAT_RGBX4444,
53324b99bd7b4d Abhinav Kumar 2022-04-26 252 DRM_FORMAT_XRGB4444,
53324b99bd7b4d Abhinav Kumar 2022-04-26 253 DRM_FORMAT_BGR888,
53324b99bd7b4d Abhinav Kumar 2022-04-26 254 DRM_FORMAT_BGRA8888,
53324b99bd7b4d Abhinav Kumar 2022-04-26 255 DRM_FORMAT_BGRX8888,
53324b99bd7b4d Abhinav Kumar 2022-04-26 256 DRM_FORMAT_ABGR1555,
53324b99bd7b4d Abhinav Kumar 2022-04-26 257 DRM_FORMAT_BGRA5551,
53324b99bd7b4d Abhinav Kumar 2022-04-26 258 DRM_FORMAT_XBGR1555,
53324b99bd7b4d Abhinav Kumar 2022-04-26 259 DRM_FORMAT_BGRX5551,
53324b99bd7b4d Abhinav Kumar 2022-04-26 260 DRM_FORMAT_ABGR4444,
53324b99bd7b4d Abhinav Kumar 2022-04-26 261 DRM_FORMAT_BGRA4444,
53324b99bd7b4d Abhinav Kumar 2022-04-26 262 DRM_FORMAT_BGRX4444,
53324b99bd7b4d Abhinav Kumar 2022-04-26 263 DRM_FORMAT_XBGR4444,
53324b99bd7b4d Abhinav Kumar 2022-04-26 264 };
53324b99bd7b4d Abhinav Kumar 2022-04-26 265
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-03-07 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 3:15 [PATCH] drm/msm/dpu: Support YUV formats on writeback for DPU 5.x+ Jessica Zhang
2025-03-06 5:06 ` Abhinav Kumar
2025-03-06 6:48 ` Dmitry Baryshkov
2025-03-07 10:20 ` kernel test robot
2025-03-07 12:30 ` kernel test robot [this message]
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=202503072004.KTOFOoOq-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_jesszhan@quicinc.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.