On 18/06/2021 16:52, Thierry Reding wrote:
On Fri, Jun 18, 2021 at 04:21:45PM +0200, kernel test robot wrote:
> tree:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: e71e3a48a7e89fa71fb70bf4602367528864d2ff
> commit: 56ebc9b0d77e0406aba2d900c82e79204cc7dc32 [5946/11253] memory: tegra: Enable
compile testing for all drivers
> config: x86_64-randconfig-a001-20210618 (attached as .config)
> compiler: clang version 13.0.0 (
https://github.com/llvm/llvm-project
64720f57bea6a6bf033feef4a5751ab9c0c3b401)
> 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 x86_64 cross compiling tool for clang build
> # apt-get install binutils-x86-64-linux-gnu
> #
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commi...
> 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 56ebc9b0d77e0406aba2d900c82e79204cc7dc32
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp(a)intel.com>
>
> Note: the linux-next/master HEAD e71e3a48a7e89fa71fb70bf4602367528864d2ff builds
fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
>>> ld.lld: error: undefined symbol: reset_controller_register
> >>> referenced by mc.c
> >>> memory/tegra/mc.o:(tegra_mc_probe) in archive
drivers/built-in.a
Ugh... more fallout from that compile-test enablement. It looks like
that compile-test stubs addition patch for reset hasn't found its way
into linux-next yet.
Does it mean reset tree is not in linux-next?
Philipp, I wonder if it would make sense for Krzysztof to pick up
that
patch or, if you prefer, for Krzysztof to pull a stable branch from you
that includes this so that the memory controller tree becomes buildable
again?
These are randconfigs, so I don't think Linus will hit them when
merging. Therefore assuming the reset-stubs are applied (and tree is in
next), we should be fine, shouldn't we?
Best regards,
Krzysztof