From: kernel test robot <lkp@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Arun R Murthy <arun.r.murthy@intel.com>
Subject: drivers/gpu/drm/i915/display/intel_lt_phy.c:246:35: sparse: sparse: Using plain integer as NULL pointer
Date: Fri, 08 May 2026 15:55:55 +0800 [thread overview]
Message-ID: <202605081525.Z4gAosfh-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 917719c412c48687d4a176965d1fa35320ec457c
commit: e1455196ada3ed892742b6b3459be7e6980a1590 drm/i915/ltphy: Read PHY_VDR_0_CONFIG register
date: 6 months ago
config: x86_64-randconfig-121-20260508 (https://download.01.org/0day-ci/archive/20260508/202605081525.Z4gAosfh-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260508/202605081525.Z4gAosfh-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
| Fixes: e1455196ada3 ("drm/i915/ltphy: Read PHY_VDR_0_CONFIG register")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202605081525.Z4gAosfh-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/display/intel_lt_phy.c:246:35: sparse: sparse: Using plain integer as NULL pointer
vim +246 drivers/gpu/drm/i915/display/intel_lt_phy.c
238
239 void intel_lt_phy_pll_enable(struct intel_encoder *encoder,
240 const struct intel_crtc_state *crtc_state)
241 {
242 struct intel_display *display = to_intel_display(encoder);
243 struct intel_digital_port *dig_port = enc_to_dig_port(encoder);
244 bool lane_reversal = dig_port->lane_reversal;
245 u8 owned_lane_mask = intel_lt_phy_get_owned_lane_mask(encoder);
> 246 intel_wakeref_t wakeref = 0;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-08 7:56 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=202605081525.Z4gAosfh-lkp@intel.com \
--to=lkp@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=suraj.kandpal@intel.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