From: kernel test robot <lkp@intel.com>
To: Yang Li <yang.lee@linux.alibaba.com>, airlied@gmail.com
Cc: oe-kbuild-all@lists.linux.dev, tvrtko.ursulin@linux.intel.com,
intel-gfx@lists.freedesktop.org,
Abaci Robot <abaci@linux.alibaba.com>,
linux-kernel@vger.kernel.org,
Yang Li <yang.lee@linux.alibaba.com>,
dri-devel@lists.freedesktop.org, rodrigo.vivi@intel.com
Subject: Re: [PATCH -next] drm/i915: remove unreachable code
Date: Thu, 1 Jun 2023 00:13:40 +0800 [thread overview]
Message-ID: <202306010001.gUxZYcyb-lkp@intel.com> (raw)
In-Reply-To: <20230531021714.125078-1-yang.lee@linux.alibaba.com>
Hi Yang,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20230530]
url: https://github.com/intel-lab-lkp/linux/commits/Yang-Li/drm-i915-remove-unreachable-code/20230531-101832
base: next-20230530
patch link: https://lore.kernel.org/r/20230531021714.125078-1-yang.lee%40linux.alibaba.com
patch subject: [PATCH -next] drm/i915: remove unreachable code
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20230601/202306010001.gUxZYcyb-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/58232a66b9d21d80bc6b478e2a8fb1443da3adfc
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Yang-Li/drm-i915-remove-unreachable-code/20230531-101832
git checkout 58232a66b9d21d80bc6b478e2a8fb1443da3adfc
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 olddefconfig
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/i915/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202306010001.gUxZYcyb-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpu/drm/i915/display/intel_color.c: In function 'intel_color_prepare_commit':
>> drivers/gpu/drm/i915/display/intel_color.c:1803:28: warning: unused variable 'crtc' [-Wunused-variable]
1803 | struct intel_crtc *crtc = to_intel_crtc(crtc_state->uapi.crtc);
| ^~~~
vim +/crtc +1803 drivers/gpu/drm/i915/display/intel_color.c
3962ca4e080a52 Ville Syrjälä 2023-03-20 1800
efb2b57edf20c3 Ville Syrjälä 2022-11-23 1801 void intel_color_prepare_commit(struct intel_crtc_state *crtc_state)
efb2b57edf20c3 Ville Syrjälä 2022-11-23 1802 {
b358c3b98813b1 Ville Syrjälä 2022-11-23 @1803 struct intel_crtc *crtc = to_intel_crtc(crtc_state->uapi.crtc);
b358c3b98813b1 Ville Syrjälä 2022-11-23 1804
2487ae0bcb53a7 Ville Syrjälä 2022-11-23 1805 /* FIXME DSB has issues loading LUTs, disable it for now */
2487ae0bcb53a7 Ville Syrjälä 2022-11-23 1806 return;
efb2b57edf20c3 Ville Syrjälä 2022-11-23 1807 }
efb2b57edf20c3 Ville Syrjälä 2022-11-23 1808
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-05-31 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 2:17 [PATCH -next] drm/i915: remove unreachable code Yang Li
2023-05-31 9:22 ` [Intel-gfx] " Andi Shyti
2023-05-31 15:32 ` kernel test robot
2023-05-31 16:13 ` 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=202306010001.gUxZYcyb-lkp@intel.com \
--to=lkp@intel.com \
--cc=abaci@linux.alibaba.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=yang.lee@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox