From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [usb:usb-testing 5/12] drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c:113:46: error: passing argument 1 of 'devm_drm_dp_hpd_bridge_add' from incompatible pointer type
Date: Sat, 11 May 2024 00:20:18 +0300 [thread overview]
Message-ID: <bq3naqyizwy24qg5zxd3mk3nlu56zm6jvothhc3c2uxllva777@k4aztvs6477x> (raw)
In-Reply-To: <202405110428.TMCfb1Ut-lkp@intel.com>
On Sat, May 11, 2024 at 04:36:30AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
> head: 344f74cf531d90245e1296b3ffbaa7df99dd18f6
> commit: 718b36a7b49acbba36546371db2d235271ceb06c [5/12] usb: typec: qcom-pmic-typec: split HPD bridge alloc and registration
> config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20240511/202405110428.TMCfb1Ut-lkp@intel.com/config)
> compiler: sh4-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240511/202405110428.TMCfb1Ut-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/202405110428.TMCfb1Ut-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c: In function 'qcom_pmic_typec_probe':
> >> drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c:113:46: error: passing argument 1 of 'devm_drm_dp_hpd_bridge_add' from incompatible pointer type [-Werror=incompatible-pointer-types]
> 113 | ret = devm_drm_dp_hpd_bridge_add(tcpm->dev, bridge_dev);
> | ~~~~^~~~~
> | |
> | struct device *
> In file included from drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c:21:
> include/drm/bridge/aux-bridge.h:36:71: note: expected 'struct auxiliary_device *' but argument is of type 'struct device *'
> 36 | static inline int devm_drm_dp_hpd_bridge_add(struct auxiliary_device *adev)
> | ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
> >> drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c:113:15: error: too many arguments to function 'devm_drm_dp_hpd_bridge_add'
> 113 | ret = devm_drm_dp_hpd_bridge_add(tcpm->dev, bridge_dev);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> include/drm/bridge/aux-bridge.h:36:19: note: declared here
> 36 | static inline int devm_drm_dp_hpd_bridge_add(struct auxiliary_device *adev)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
There is an error in include/drm/bridge/aux-bridge.h in the definition
of the stub. I'll send a patch.
--
With best wishes
Dmitry
prev parent reply other threads:[~2024-05-10 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 20:36 [usb:usb-testing 5/12] drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c:113:46: error: passing argument 1 of 'devm_drm_dp_hpd_bridge_add' from incompatible pointer type kernel test robot
2024-05-10 21:20 ` Dmitry Baryshkov [this message]
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=bq3naqyizwy24qg5zxd3mk3nlu56zm6jvothhc3c2uxllva777@k4aztvs6477x \
--to=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=johan+linaro@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).