From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Biju Das <biju.das.jz@bp.renesas.com>, kernel test robot <lkp@intel.com>
Cc: "llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
Linux Memory Management List <linux-mm@kvack.org>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [linux-next:master 5636/9540] ld.lld: error: undefined symbol: drm_of_get_data_lanes_count_ep
Date: Wed, 23 Nov 2022 16:50:07 +0800 [thread overview]
Message-ID: <0a033967-0336-b265-e346-e05eec14e204@intel.com> (raw)
In-Reply-To: <OS0PR01MB59222B2AADF54D1E41D81897860D9@OS0PR01MB5922.jpnprd01.prod.outlook.com>
On 11/22/2022 11:17 PM, Biju Das wrote:
> Hi kernel test robot,
>
>> Subject: [linux-next:master 5636/9540] ld.lld: error: undefined symbol:
>> drm_of_get_data_lanes_count_ep
>>
>> tree:
>>
>> head: 771a207d1ee9f38da8c0cee1412228f18b900bac
>> commit: 7a043f978ed1433bddb088a732e9bb91501ebd76 [5636/9540] drm: rcar-
>> du: Add RZ/G2L DSI driver
>> config: arm64-randconfig-r026-20221122
>> compiler: clang version 16.0.0
>> reproduce (this is a W=1 build):
>> wget
> -O ~/bin/make.cross
>> chmod +x ~/bin/make.cross
>> # install arm64 cross compiling tool for clang build
>> # apt-get install binutils-aarch64-linux-gnu
>> #
>> git remote add linux-next
>> git fetch --no-tags linux-next master
>> git checkout 7a043f978ed1433bddb088a732e9bb91501ebd76
>> # 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 SHELL=/bin/bash
>>
>> If you fix the issue, kindly add following tag where applicable
>> | Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>>>> ld.lld: error: undefined symbol: drm_of_get_data_lanes_count_ep
>> >>> referenced by rzg2l_mipi_dsi.c
>> >>> drivers/gpu/drm/rcar-
>> du/rzg2l_mipi_dsi.o:(rzg2l_mipi_dsi_probe) in archive vmlinux.a
>> --
>>>> ld.lld: error: undefined symbol: drm_bridge_attach
>> >>> referenced by rzg2l_mipi_dsi.c
>> >>> drivers/gpu/drm/rcar-
>> du/rzg2l_mipi_dsi.o:(rzg2l_mipi_dsi_attach) in archive vmlinux.a
>> --
>>>> ld.lld: error: undefined symbol:
>> drm_atomic_get_new_connector_for_encoder
>> >>> referenced by rzg2l_mipi_dsi.c
>> >>> drivers/gpu/drm/rcar-
>> du/rzg2l_mipi_dsi.o:(rzg2l_mipi_dsi_atomic_enable) in archive vmlinux.a
>> --
>>>> ld.lld: error: undefined symbol: devm_drm_of_get_bridge
>> >>> referenced by rzg2l_mipi_dsi.c
>> >>> drivers/gpu/drm/rcar-
>> du/rzg2l_mipi_dsi.o:(rzg2l_mipi_dsi_host_attach) in archive vmlinux.a
>> --
>>>> ld.lld: error: undefined symbol: drm_bridge_add
>> >>> referenced by rzg2l_mipi_dsi.c
>> >>> drivers/gpu/drm/rcar-
>> du/rzg2l_mipi_dsi.o:(rzg2l_mipi_dsi_host_attach) in archive vmlinux.a
>> --
>>>> ld.lld: error: undefined symbol: drm_bridge_remove
>> >>> referenced by rzg2l_mipi_dsi.c
>> >>> drivers/gpu/drm/rcar-
>> du/rzg2l_mipi_dsi.o:(rzg2l_mipi_dsi_host_detach) in archive vmlinux.a
>> --
>>>> ld.lld: error: undefined symbol:
>> drm_atomic_helper_bridge_duplicate_state
>> >>> referenced by rzg2l_mipi_dsi.c
>> >>> drivers/gpu/drm/rcar-
>> du/rzg2l_mipi_dsi.o:(rzg2l_mipi_dsi_bridge_ops) in archive vmlinux.a
>> --
>>>> ld.lld: error: undefined symbol:
>> drm_atomic_helper_bridge_destroy_state
>> >>> referenced by rzg2l_mipi_dsi.c
>> >>> drivers/gpu/drm/rcar-
>> du/rzg2l_mipi_dsi.o:(rzg2l_mipi_dsi_bridge_ops) in archive vmlinux.a
>> --
>>>> ld.lld: error: undefined symbol: drm_atomic_helper_bridge_reset
>> >>> referenced by rzg2l_mipi_dsi.c
>> >>> drivers/gpu/drm/rcar-
>> du/rzg2l_mipi_dsi.o:(rzg2l_mipi_dsi_bridge_ops) in archive vmlinux.a
>
> I was able to reproduce the issue and the same fix[1], will fix the issue
> here for clang compiler as well. Can you please apply [1] to avoid
> repeatedly sending the same issue for different compilers on the kernel test robot?
Hi Biju,
Thanks for your advice, we'll add it to ignore list.
Best Regards,
Rong Chen
>
> [1] https://lore.kernel.org/linux-renesas-soc/Y3wVLU01mHp2zozI@pendragon.ideasonboard.com/T/#t
>
> Cheers,
> Biju
>
prev parent reply other threads:[~2022-11-23 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 13:30 [linux-next:master 5636/9540] ld.lld: error: undefined symbol: drm_of_get_data_lanes_count_ep kernel test robot
2022-11-22 15:17 ` Biju Das
2022-11-23 8:50 ` Chen, Rong A [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=0a033967-0336-b265-e346-e05eec14e204@intel.com \
--to=rong.a.chen@intel.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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 NNTP newsgroup(s).