From: kernel test robot <lkp@intel.com>
To: Brandon Cheo Fusi <fusibrandon13@gmail.com>, maxime@cerno.tech
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
airlied@gmail.com, andrzej.hajda@intel.com, daniel@ffwll.ch,
dave.stevenson@raspberrypi.com, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, jagan@amarulasolutions.com,
jernej.skrabec@gmail.com, krzysztof.kozlowski+dt@linaro.org,
linux-amarula@amarulasolutions.com,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, maarten.lankhorst@linux.intel.com,
marex@denx.de, neil.armstrong@linaro.org, rfoss@kernel.org,
robh+dt@kernel.org, sam@ravnborg.org, samuel@sholland.org,
tzimmermann@suse.de, wens@csie.org,
Brandon Cheo Fusi <fusibrandon13@gmail.com>
Subject: Re: [PATCH 1/2] drm: sun4i/dsi: factor out DSI PHY poweron and poweroff
Date: Tue, 11 Apr 2023 00:25:23 +0800 [thread overview]
Message-ID: <202304110053.n5nu03YZ-lkp@intel.com> (raw)
In-Reply-To: <20230410084750.164016-2-fusibrandon13@gmail.com>
Hi Brandon,
kernel test robot noticed the following build errors:
[auto build test ERROR on sunxi/sunxi/for-next]
[also build test ERROR on linus/master v6.3-rc6 next-20230406]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Brandon-Cheo-Fusi/drm-sun4i-dsi-factor-out-DSI-PHY-poweron-and-poweroff/20230410-165257
base: https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git sunxi/for-next
patch link: https://lore.kernel.org/r/20230410084750.164016-2-fusibrandon13%40gmail.com
patch subject: [PATCH 1/2] drm: sun4i/dsi: factor out DSI PHY poweron and poweroff
config: arm64-randconfig-r002-20230410 (https://download.01.org/0day-ci/archive/20230411/202304110053.n5nu03YZ-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project 2c57868e2e877f73c339796c3374ae660bb77f0d)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://github.com/intel-lab-lkp/linux/commit/afa9cb6821e4527f07c10a777ea44e380b524858
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Brandon-Cheo-Fusi/drm-sun4i-dsi-factor-out-DSI-PHY-poweron-and-poweroff/20230410-165257
git checkout afa9cb6821e4527f07c10a777ea44e380b524858
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/gpu/drm/sun4i/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304110053.n5nu03YZ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c:843:13: error: incompatible function pointer types initializing 'void (*)(struct drm_encoder *)' with an expression of type 'void (struct drm_encoder *, struct drm_atomic_state *)' [-Wincompatible-function-pointer-types]
.enable = sun6i_dsi_encoder_enable,
^~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +843 drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c
133add5b5ad42b Maxime Ripard 2018-04-04 841
133add5b5ad42b Maxime Ripard 2018-04-04 842 static const struct drm_encoder_helper_funcs sun6i_dsi_enc_helper_funcs = {
133add5b5ad42b Maxime Ripard 2018-04-04 @843 .enable = sun6i_dsi_encoder_enable,
133add5b5ad42b Maxime Ripard 2018-04-04 844 };
133add5b5ad42b Maxime Ripard 2018-04-04 845
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-04-10 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 8:47 [PATCH 0/2] drm: sun4i/dsi: allow modeset helpers to manage display Brandon Cheo Fusi
2023-04-10 8:47 ` [PATCH 1/2] drm: sun4i/dsi: factor out DSI PHY poweron and poweroff Brandon Cheo Fusi
2023-04-10 16:25 ` kernel test robot [this message]
2023-04-10 17:57 ` kernel test robot
2023-04-10 8:47 ` [PATCH 2/2] drm: sun4i: tie DSI PHY Poweron/off to crtc enable/disable Brandon Cheo Fusi
2023-04-11 15:24 ` [PATCH 0/2] drm: sun4i/dsi: allow modeset helpers to manage display Maxime Ripard
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=202304110053.n5nu03YZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dave.stevenson@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fusibrandon13@gmail.com \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=llvm@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@denx.de \
--cc=maxime@cerno.tech \
--cc=neil.armstrong@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rfoss@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=samuel@sholland.org \
--cc=tzimmermann@suse.de \
--cc=wens@csie.org \
/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 NNTP newsgroup(s).