From: kernel test robot <lkp@intel.com>
To: " Michał Grzelak" <michal.grzelak@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>
Subject: drivers/gpu/drm/i915/display/intel_bios.c:3899:20: warning: variable 'vspeo' is uninitialized when used here
Date: Thu, 11 Jun 2026 17:18:27 +0200 [thread overview]
Message-ID: <202606111734.HRShsb0i-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Micha-Grzelak/drm-i915-bios-search-for-VBT-57-by-default/20260609-035533
head: 37e5f3711f75121bd6a54baa6a92299c51fc313c
commit: 703adad1fcf91efe93f2e1bf885dd23d33cc642c drm/i915: override Snps's VS/PE when requested
date: 3 days ago
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260611/202606111734.HRShsb0i-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project f43d6834093b19baf79beda8c0337ab020ac5f17)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260611/202606111734.HRShsb0i-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/202606111734.HRShsb0i-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/i915/display/intel_bios.c:3899:20: warning: variable 'vspeo' is uninitialized when used here [-Wuninitialized]
3899 | entries = (void *)vspeo->entries;
| ^~~~~
drivers/gpu/drm/i915/display/intel_bios.c:3891:35: note: initialize the variable 'vspeo' to silence this warning
3891 | struct intel_ddi_buf_trans *vspeo;
| ^
| = NULL
1 warning generated.
vim +/vspeo +3899 drivers/gpu/drm/i915/display/intel_bios.c
3883
3884 const struct intel_ddi_buf_trans *
3885 intel_bios_get_c20_vspeo(const struct intel_bios_encoder_data *devdata,
3886 bool has_dp, bool is_uhbr)
3887 {
3888 struct intel_display *display;
3889 union intel_ddi_buf_trans_entry *entries;
3890 int num_columns, num_rows, level, idx;
3891 struct intel_ddi_buf_trans *vspeo;
3892 const u32 *tables;
3893 size_t offset = 0;
3894
3895 if (!validate_vspeo(devdata, has_dp))
3896 return NULL;
3897
3898 display = devdata->display;
> 3899 entries = (void *)vspeo->entries;
3900 tables = display->vbt.vspeo.tables;
3901 num_columns = display->vbt.vspeo.num_columns;
3902 num_rows = display->vbt.vspeo.num_rows;
3903 idx = is_uhbr ? 5 : 4;
3904
3905 offset += idx * num_rows * num_columns;
3906
3907 for (level = 0; level < num_rows; level++) {
3908 u32 vswing = tables[offset];
3909 u32 pre_cursor = tables[offset + 1];
3910 u32 post_cursor = tables[offset + 2];
3911
3912 entries[level].snps.vswing = vswing;
3913 entries[level].snps.pre_cursor = pre_cursor;
3914 entries[level].snps.post_cursor = post_cursor;
3915
3916 offset += num_columns;
3917 }
3918
3919 return vspeo;
3920 }
3921
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-11 15:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202606111734.HRShsb0i-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=michal.grzelak@intel.com \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox