linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: kernel test robot <lkp@intel.com>,
	Brian Norris <briannorris@chromium.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Douglas Anderson <dianders@chromium.org>
Subject: Re: [linux-next:master 9269/14079] ld.lld: error: undefined symbol: rockchip_pmu_block
Date: Wed, 25 May 2022 10:04:14 +0900	[thread overview]
Message-ID: <18b1bfe6-d844-d2c2-fc5e-40248aaf72be@samsung.com> (raw)
In-Reply-To: <202205241931.GbIyyVs2-lkp@intel.com>

Hi Brian,

How can fix this build issue? 
Should I add the ARCH_ROCKCHIP dependency to rk3399_dmc.c?


On 5/24/22 8:49 PM, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   09ce5091ff971cdbfd67ad84dc561ea27f10d67a
> commit: 2e691421a2c9e0462175fe98171afa632861b199 [9269/14079] PM / devfreq: rk3399_dmc: Block PMU during transitions
> config: arm64-randconfig-r006-20220524 (https://protect2.fireeye.com/v1/url?k=d0aebf16-b1d51581-d0af3459-74fe4860001d-afa265d9beca802e&q=1&e=5a47bbdc-1a5f-45df-a343-9f76a9f3e3c8&u=https%3A%2F%2Fdownload.01.org%2F0day-ci%2Farchive%2F20220524%2F202205241931.GbIyyVs2-lkp%40intel.com%2Fconfig)
> compiler: clang version 15.0.0 (https://protect2.fireeye.com/v1/url?k=207af339-410159ae-207b7876-74fe4860001d-c3c991f126566568&q=1&e=5a47bbdc-1a5f-45df-a343-9f76a9f3e3c8&u=https%3A%2F%2Fgithub.com%2Fllvm%2Fllvm-project 10c9ecce9f6096e18222a331c5e7d085bd813f75)
> reproduce (this is a W=1 build):
>         wget https://protect2.fireeye.com/v1/url?k=e74a1a4c-8631b0db-e74b9103-74fe4860001d-3ba2876fc53e7fc8&q=1&e=5a47bbdc-1a5f-45df-a343-9f76a9f3e3c8&u=https%3A%2F%2Fraw.githubusercontent.com%2Fintel%2Flkp-tests%2Fmaster%2Fsbin%2Fmake.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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2e691421a2c9e0462175fe98171afa632861b199
>         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 2e691421a2c9e0462175fe98171afa632861b199
>         # 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>
> 
> Note: the linux-next/master HEAD 09ce5091ff971cdbfd67ad84dc561ea27f10d67a builds fine.
>       It may have been fixed somewhere.
> 
> All errors (new ones prefixed by >>):
> 
>>> ld.lld: error: undefined symbol: rockchip_pmu_block
>    >>> referenced by rk3399_dmc.c:101 (drivers/devfreq/rk3399_dmc.c:101)
>    >>> devfreq/rk3399_dmc.o:(rk3399_dmcfreq_target) in archive drivers/built-in.a
> --
>>> ld.lld: error: undefined symbol: rockchip_pmu_unblock
>    >>> referenced by rk3399_dmc.c:212 (drivers/devfreq/rk3399_dmc.c:212)
>    >>> devfreq/rk3399_dmc.o:(rk3399_dmcfreq_target) in archive drivers/built-in.a
> 


-- 
Best Regards,
Chanwoo Choi
Samsung Electronics


  reply	other threads:[~2022-05-25  1:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220524114954epcas1p416e486dce031a941263b13120e717d72@epcas1p4.samsung.com>
2022-05-24 11:49 ` kernel test robot
2022-05-25  1:04   ` Chanwoo Choi [this message]
2022-05-25  1:16     ` Brian Norris
2022-05-25  3:09       ` Chanwoo Choi

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=18b1bfe6-d844-d2c2-fc5e-40248aaf72be@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=briannorris@chromium.org \
    --cc=dianders@chromium.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=llvm@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