From: Lyude Paul <lyude@redhat.com>
To: kernel test robot <lkp@intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 3267/10468] drm_dp_mst_topology.c:undefined reference to `__drm_atomic_helper_private_obj_duplicate_state'
Date: Fri, 04 Mar 2022 15:26:24 -0500 [thread overview]
Message-ID: <179f145abd233bfc3f9ca36e77689780294c9d3c.camel@redhat.com> (raw)
In-Reply-To: <202203040403.CjBmY9Vq-lkp@intel.com>
Thomas, I assume this is on your radar?
On Fri, 2022-03-04 at 10:47 +0800, kernel test robot wrote:
> Hi Thomas,
>
> FYI, the error/warning still remains.
>
> tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 91265a6da44d13296bdb5b3fbafa19d06be462f2
> commit: eea89dff4c39a106f98d1cb5e4d626f8c63908b9 [3267/10468] drm/panel:
> Select DRM_DP_HELPER for DRM_PANEL_EDP
> config: arm-qcom_defconfig
> (https://download.01.org/0day-ci/archive/20220304/202203040403.CjBmY9Vq-lkp@
> intel.com/config)
> compiler: arm-linux-gnueabi-gcc (GCC) 11.2.0
> 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
> #
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=eea89dff4c39a106f98d1cb5e4d626f8c63908b9
> git remote add linux-next
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout eea89dff4c39a106f98d1cb5e4d626f8c63908b9
> # save the config file to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross
> O=build_dir ARCH=arm SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> arm-linux-gnueabi-ld: drivers/gpu/drm/dp/drm_dp_mst_topology.o: in
> function `drm_dp_mst_duplicate_state':
> > > drm_dp_mst_topology.c:(.text+0x2db0): undefined reference to
> > > `__drm_atomic_helper_private_obj_duplicate_state'
> arm-linux-gnueabi-ld: drivers/gpu/drm/dp/drm_dp_mst_topology.o: in
> function `drm_dp_delayed_destroy_work':
> > > drm_dp_mst_topology.c:(.text+0x36c4): undefined reference to
> > > `drm_kms_helper_hotplug_event'
> arm-linux-gnueabi-ld: drivers/gpu/drm/dp/drm_dp_mst_topology.o: in
> function `drm_dp_mst_up_req_work':
> drm_dp_mst_topology.c:(.text+0x7888): undefined reference to
> `drm_kms_helper_hotplug_event'
> arm-linux-gnueabi-ld: drivers/gpu/drm/dp/drm_dp_mst_topology.o: in
> function `drm_dp_mst_link_probe_work':
> drm_dp_mst_topology.c:(.text+0x8220): undefined reference to
> `drm_kms_helper_hotplug_event'
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
next prev parent reply other threads:[~2022-03-04 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 2:47 kernel test robot
2022-03-04 20:26 ` Lyude Paul [this message]
2022-03-14 19:05 ` Thomas Zimmermann
2022-03-16 16:07 ` Brian Masney
2022-03-16 19:08 ` Thomas Zimmermann
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=179f145abd233bfc3f9ca36e77689780294c9d3c.camel@redhat.com \
--to=lyude@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=tzimmermann@suse.de \
/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