linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Luca Ceresoli <luca.ceresoli@bootlin.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Adam Ford <aford173@gmail.com>
Subject: [linux-next:master 3985/4465] drivers/gpu/drm/bridge/imx/imx8mp-hdmi-pvi.c:113:24: sparse: sparse: Using plain integer as NULL pointer
Date: Tue, 6 Feb 2024 21:59:18 +0800	[thread overview]
Message-ID: <202402062134.a6CqAt3s-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   ac139fc7db67968e5061715508b5fc4aa7c40c56
commit: 059c53e877ca6e723e10490c27c1487a63e66efe [3985/4465] drm/bridge: imx: add driver for HDMI TX Parallel Video Interface
config: arc-randconfig-r113-20240206 (https://download.01.org/0day-ci/archive/20240206/202402062134.a6CqAt3s-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240206/202402062134.a6CqAt3s-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/202402062134.a6CqAt3s-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/bridge/imx/imx8mp-hdmi-pvi.c:113:24: sparse: sparse: Using plain integer as NULL pointer
   drivers/gpu/drm/bridge/imx/imx8mp-hdmi-pvi.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/stackdepot.h, ...):
   include/linux/page-flags.h:242:46: sparse: sparse: self-comparison always evaluates to false

vim +113 drivers/gpu/drm/bridge/imx/imx8mp-hdmi-pvi.c

    99	
   100	static u32 *
   101	imx8mp_hdmi_pvi_bridge_get_input_bus_fmts(struct drm_bridge *bridge,
   102						  struct drm_bridge_state *bridge_state,
   103						  struct drm_crtc_state *crtc_state,
   104						  struct drm_connector_state *conn_state,
   105						  u32 output_fmt,
   106						  unsigned int *num_input_fmts)
   107	{
   108		struct imx8mp_hdmi_pvi *pvi = to_imx8mp_hdmi_pvi(bridge);
   109		struct drm_bridge *next_bridge = pvi->next_bridge;
   110		struct drm_bridge_state *next_state;
   111	
   112		if (!next_bridge->funcs->atomic_get_input_bus_fmts)
 > 113			return 0;
   114	
   115		next_state = drm_atomic_get_new_bridge_state(crtc_state->state,
   116							     next_bridge);
   117	
   118		return next_bridge->funcs->atomic_get_input_bus_fmts(next_bridge,
   119								     next_state,
   120								     crtc_state,
   121								     conn_state,
   122								     output_fmt,
   123								     num_input_fmts);
   124	}
   125	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2024-02-06 14:00 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=202402062134.a6CqAt3s-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aford173@gmail.com \
    --cc=l.stach@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-mm@kvack.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=neil.armstrong@linaro.org \
    --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