From: Dmitry Osipenko <digetx@gmail.com>
To: kernel test robot <lkp@intel.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v1 2/2] memory: tegra: Enable compile testing for all drivers
Date: Tue, 11 May 2021 19:22:56 +0300 [thread overview]
Message-ID: <d0b84024-2f91-bc0a-8d3b-ec342ac4812d@gmail.com> (raw)
In-Reply-To: <202105112327.nAMH7lzl-lkp@intel.com>
11.05.2021 18:43, kernel test robot пишет:
> Hi Dmitry,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on tegra/for-next]
> [also build test ERROR on v5.13-rc1 next-20210511]
> [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]
>
> url: https://github.com/0day-ci/linux/commits/Dmitry-Osipenko/Enable-compile-testing-for-Tegra-memory-drivers/20210511-053910
> base: https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git for-next
> config: parisc-randconfig-r011-20210511 (attached as .config)
> compiler: hppa64-linux-gcc (GCC) 9.3.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://github.com/0day-ci/linux/commit/ecd67b1d49eb33c9821130a2b3b896bab395118d
> git remote add linux-review https://github.com/0day-ci/linux
> git fetch --no-tags linux-review Dmitry-Osipenko/Enable-compile-testing-for-Tegra-memory-drivers/20210511-053910
> git checkout ecd67b1d49eb33c9821130a2b3b896bab395118d
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=parisc
>
> 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 >>):
>
> hppa64-linux-ld: drivers/memory/tegra/tegra20-emc.o: in function `.LC9':
>>> (.data.rel.ro+0x30): undefined reference to `tegra20_clk_set_emc_round_callback'
> hppa64-linux-ld: drivers/memory/tegra/tegra20-emc.o: in function `.LC52':
> (.data.rel.ro+0xe0): undefined reference to `tegra20_clk_set_emc_round_callback'
> hppa64-linux-ld: drivers/memory/tegra/tegra30-emc.o: in function `.LC11':
>>> (.data.rel.ro+0x30): undefined reference to `tegra20_clk_set_emc_round_callback'
> hppa64-linux-ld: drivers/memory/tegra/tegra30-emc.o: in function `.LC48':
> (.data.rel.ro+0xd0): undefined reference to `tegra20_clk_set_emc_round_callback'
> hppa64-linux-ld: drivers/memory/tegra/tegra30-emc.o: in function `.LC60':
>>> (.data.rel.ro+0x118): undefined reference to `tegra20_clk_prepare_emc_mc_same_freq'
> hppa64-linux-ld: drivers/memory/tegra/tegra124-emc.o: in function `.LC3':
>>> (.data.rel.ro+0x10): undefined reference to `tegra124_clk_set_emc_callbacks'
> hppa64-linux-ld: drivers/memory/tegra/tegra124-emc.o: in function `.LC55':
> (.data.rel.ro+0x110): undefined reference to `tegra124_clk_set_emc_callbacks'
>
> Kconfig warnings: (for reference only)
> WARNING: unmet direct dependencies detected for TEGRA124_CLK_EMC
> Depends on COMMON_CLK
> Selected by
> - TEGRA124_EMC && MEMORY && TEGRA_MC && (ARCH_TEGRA_124_SOC || COMPILE_TEST
I'll fix these missing stubs in v2.
next prev parent reply other threads:[~2021-05-11 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 21:37 [PATCH v1 0/2] Enable compile-testing for Tegra memory drivers Dmitry Osipenko
2021-05-10 21:37 ` [PATCH v1 1/2] soc/tegra: fuse: Add missing stubs Dmitry Osipenko
2021-05-10 21:37 ` [PATCH v1 2/2] memory: tegra: Enable compile testing for all drivers Dmitry Osipenko
2021-05-11 13:58 ` kernel test robot
2021-05-11 15:17 ` Dmitry Osipenko
2021-05-11 15:31 ` Krzysztof Kozlowski
2021-05-11 16:00 ` Dmitry Osipenko
2021-05-11 17:35 ` Nathan Chancellor
2021-05-11 17:57 ` Krzysztof Kozlowski
2021-05-11 18:36 ` Dmitry Osipenko
2021-05-11 15:43 ` kernel test robot
2021-05-11 16:22 ` Dmitry Osipenko [this message]
2021-05-11 16:41 ` Krzysztof Kozlowski
2021-05-11 18:30 ` Dmitry Osipenko
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=d0b84024-2f91-bc0a-8d3b-ec342ac4812d@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lkp@intel.com \
--cc=thierry.reding@gmail.com \
/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