From: kernel test robot <lkp@intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: [linux-next:master 4248/4884] include/drm/bridge/aux-bridge.h:29:16: sparse: sparse: Using plain integer as NULL pointer
Date: Wed, 6 Dec 2023 01:00:04 +0800 [thread overview]
Message-ID: <202312060025.BdeqZrWx-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 0f5f12ac05f36f117e793656c3f560625e927f1b
commit: 7d9f1b72b29698e3030c2b163522cf4aa91b47e9 [4248/4884] usb: typec: qcom-pmic-typec: switch to DRM_AUX_HPD_BRIDGE
config: sh-randconfig-r112-20231205 (https://download.01.org/0day-ci/archive/20231206/202312060025.BdeqZrWx-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231206/202312060025.BdeqZrWx-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/202312060025.BdeqZrWx-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c: note: in included file:
>> include/drm/bridge/aux-bridge.h:29:16: sparse: sparse: Using plain integer as NULL pointer
vim +29 include/drm/bridge/aux-bridge.h
2a04739139b2b2 Dmitry Baryshkov 2023-12-03 20
e560518a6c2e60 Dmitry Baryshkov 2023-12-03 21 #if IS_ENABLED(CONFIG_DRM_AUX_HPD_BRIDGE)
e560518a6c2e60 Dmitry Baryshkov 2023-12-03 22 struct device *drm_dp_hpd_bridge_register(struct device *parent,
e560518a6c2e60 Dmitry Baryshkov 2023-12-03 23 struct device_node *np);
e560518a6c2e60 Dmitry Baryshkov 2023-12-03 24 void drm_aux_hpd_bridge_notify(struct device *dev, enum drm_connector_status status);
e560518a6c2e60 Dmitry Baryshkov 2023-12-03 25 #else
e560518a6c2e60 Dmitry Baryshkov 2023-12-03 26 static inline struct device *drm_dp_hpd_bridge_register(struct device *parent,
e560518a6c2e60 Dmitry Baryshkov 2023-12-03 27 struct device_node *np)
e560518a6c2e60 Dmitry Baryshkov 2023-12-03 28 {
e560518a6c2e60 Dmitry Baryshkov 2023-12-03 @29 return 0;
e560518a6c2e60 Dmitry Baryshkov 2023-12-03 30 }
e560518a6c2e60 Dmitry Baryshkov 2023-12-03 31
:::::: The code at line 29 was first introduced by commit
:::::: e560518a6c2e60f1566473c146fddcff3281f617 drm/bridge: implement generic DP HPD bridge
:::::: TO: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
:::::: CC: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-05 17:01 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=202312060025.BdeqZrWx-lkp@intel.com \
--to=lkp@intel.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-mm@kvack.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