From: kernel test robot <lkp@intel.com>
To: Icenowy Zheng <uwu@icenowy.me>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: drivers/gpu/drm/verisilicon/vs_bridge.c:325:9-16: WARNING: ERR_CAST can be used with bridge
Date: Tue, 30 Jun 2026 16:51:23 +0800 [thread overview]
Message-ID: <202606301646.QdPI1IbT-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: dc59e4fea9d83f03bad6bddf3fa2e52491777482
commit: dbf21777caa8b8c88c12f7f036b01208fec0d55a drm: verisilicon: add a driver for Verisilicon display controllers
date: 5 months ago
config: parisc-randconfig-r063-20260630 (https://download.01.org/0day-ci/archive/20260630/202606301646.QdPI1IbT-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 15.2.0
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: dbf21777caa8 ("drm: verisilicon: add a driver for Verisilicon display controllers")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606301646.QdPI1IbT-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/verisilicon/vs_bridge.c:325:9-16: WARNING: ERR_CAST can be used with bridge
vim +325 drivers/gpu/drm/verisilicon/vs_bridge.c
288
289 struct vs_bridge *vs_bridge_init(struct drm_device *drm_dev,
290 struct vs_crtc *crtc)
291 {
292 unsigned int output = crtc->id;
293 struct vs_bridge *bridge;
294 struct drm_bridge *next;
295 enum vs_bridge_output_interface intf;
296 const struct drm_bridge_funcs *bridge_funcs;
297 int ret, enctype;
298
299 intf = vs_bridge_detect_output_interface(drm_dev->dev->of_node,
300 output);
301 if (intf == -ENODEV) {
302 drm_dbg(drm_dev, "Skipping output %u\n", output);
303 return NULL;
304 }
305
306 next = devm_drm_of_get_bridge(drm_dev->dev, drm_dev->dev->of_node,
307 output, intf);
308 if (IS_ERR(next)) {
309 ret = PTR_ERR(next);
310 if (ret != -EPROBE_DEFER)
311 drm_err(drm_dev,
312 "Cannot get downstream bridge of output %u\n",
313 output);
314 return ERR_PTR(ret);
315 }
316
317 if (intf == VSDC_OUTPUT_INTERFACE_DPI)
318 bridge_funcs = &vs_dpi_bridge_funcs;
319 else
320 bridge_funcs = &vs_dp_bridge_funcs;
321
322 bridge = devm_drm_bridge_alloc(drm_dev->dev, struct vs_bridge, base,
323 bridge_funcs);
324 if (IS_ERR(bridge))
> 325 return ERR_PTR(PTR_ERR(bridge));
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-30 8:51 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=202606301646.QdPI1IbT-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tzimmermann@suse.de \
--cc=uwu@icenowy.me \
/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