All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: kernel test robot <lkp@intel.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: kbuild-all@lists.01.org, linux-pm@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH v1 5/5] cpuidle: tegra: Enable compile testing
Date: Wed, 16 Jun 2021 22:45:40 +0300	[thread overview]
Message-ID: <4de3f38b-72be-b7d7-a291-0da75dc8455d@gmail.com> (raw)
In-Reply-To: <ced4dd2f-770e-95a1-f4ee-9d3f9d50087d@gmail.com>

16.06.2021 22:24, Dmitry Osipenko пишет:
> 16.06.2021 10:37, 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 next-20210615]
>> [cannot apply to pm/linux-next daniel.lezcano/clockevents/next v5.13-rc6]
>> [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/Compile-test-NVIDIA-Tegra-CPUIDLE-driver/20210607-063217
>> base:   https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git for-next
>> config: arm-randconfig-r005-20210616 (attached as .config)
>> compiler: arm-linux-gnueabi-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/53a9ab1dfd605ffae44d67f01a07a18b8ecbb1be
>>         git remote add linux-review https://github.com/0day-ci/linux
>>         git fetch --no-tags linux-review Dmitry-Osipenko/Compile-test-NVIDIA-Tegra-CPUIDLE-driver/20210607-063217
>>         git checkout 53a9ab1dfd605ffae44d67f01a07a18b8ecbb1be
>>         # save the attached .config to linux build tree
>>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm 
>>
>> 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: arch/arm/kernel/sleep.o: in function `__cpu_suspend':
>>>> (.text+0x68): undefined reference to `cpu_sa110_suspend_size'
>>    arm-linux-gnueabi-ld: arch/arm/kernel/suspend.o: in function `__cpu_suspend_save':
>>>> suspend.c:(.text+0x118): undefined reference to `cpu_sa110_do_suspend'
>>>> arm-linux-gnueabi-ld: suspend.c:(.text+0x13c): undefined reference to `cpu_sa110_do_resume'
> 
> I can't find where cpu_sa110_do_resume is specified in kernel.
> 
>> Kconfig warnings: (for reference only)
>>    WARNING: unmet direct dependencies detected for ARM_CPU_SUSPEND
>>    Depends on ARCH_SUSPEND_POSSIBLE
>>    Selected by
>>    - ARM_TEGRA_CPUIDLE && CPU_IDLE && (ARM || ARM64) && (ARCH_TEGRA || COMPILE_TEST && !ARM64
> 
> There are other Kconfig.arm entries that are compile-tested and select
> ARM_CPU_SUSPEND. Do they get the same warning? Should I do something
> about it?

Although, I see now that the other entries have dependencies which
should protect them indirectly from this warning. Perhaps adding
dependency on MMU, like QCOM driver does it, should help. I'll fix it in
the next version.

WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Osipenko <digetx@gmail.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v1 5/5] cpuidle: tegra: Enable compile testing
Date: Wed, 16 Jun 2021 22:45:40 +0300	[thread overview]
Message-ID: <4de3f38b-72be-b7d7-a291-0da75dc8455d@gmail.com> (raw)
In-Reply-To: <ced4dd2f-770e-95a1-f4ee-9d3f9d50087d@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2867 bytes --]

16.06.2021 22:24, Dmitry Osipenko пишет:
> 16.06.2021 10:37, 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 next-20210615]
>> [cannot apply to pm/linux-next daniel.lezcano/clockevents/next v5.13-rc6]
>> [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/Compile-test-NVIDIA-Tegra-CPUIDLE-driver/20210607-063217
>> base:   https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git for-next
>> config: arm-randconfig-r005-20210616 (attached as .config)
>> compiler: arm-linux-gnueabi-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/53a9ab1dfd605ffae44d67f01a07a18b8ecbb1be
>>         git remote add linux-review https://github.com/0day-ci/linux
>>         git fetch --no-tags linux-review Dmitry-Osipenko/Compile-test-NVIDIA-Tegra-CPUIDLE-driver/20210607-063217
>>         git checkout 53a9ab1dfd605ffae44d67f01a07a18b8ecbb1be
>>         # save the attached .config to linux build tree
>>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm 
>>
>> 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: arch/arm/kernel/sleep.o: in function `__cpu_suspend':
>>>> (.text+0x68): undefined reference to `cpu_sa110_suspend_size'
>>    arm-linux-gnueabi-ld: arch/arm/kernel/suspend.o: in function `__cpu_suspend_save':
>>>> suspend.c:(.text+0x118): undefined reference to `cpu_sa110_do_suspend'
>>>> arm-linux-gnueabi-ld: suspend.c:(.text+0x13c): undefined reference to `cpu_sa110_do_resume'
> 
> I can't find where cpu_sa110_do_resume is specified in kernel.
> 
>> Kconfig warnings: (for reference only)
>>    WARNING: unmet direct dependencies detected for ARM_CPU_SUSPEND
>>    Depends on ARCH_SUSPEND_POSSIBLE
>>    Selected by
>>    - ARM_TEGRA_CPUIDLE && CPU_IDLE && (ARM || ARM64) && (ARCH_TEGRA || COMPILE_TEST && !ARM64
> 
> There are other Kconfig.arm entries that are compile-tested and select
> ARM_CPU_SUSPEND. Do they get the same warning? Should I do something
> about it?

Although, I see now that the other entries have dependencies which
should protect them indirectly from this warning. Perhaps adding
dependency on MMU, like QCOM driver does it, should help. I'll fix it in
the next version.

  reply	other threads:[~2021-06-16 19:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-06 22:28 [PATCH v1 0/5] Compile-test NVIDIA Tegra CPUIDLE driver Dmitry Osipenko
2021-06-06 22:28 ` [PATCH v1 1/5] soc/tegra: fuse: Add stubs needed for compile testing Dmitry Osipenko
2021-06-06 22:28 ` [PATCH v1 2/5] soc/tegra: irq: " Dmitry Osipenko
2021-06-16 19:06   ` Daniel Lezcano
2021-06-16 19:17     ` Dmitry Osipenko
2021-06-16 19:18       ` Daniel Lezcano
2021-06-06 22:28 ` [PATCH v1 3/5] soc/tegra: pm: Make stubs usable " Dmitry Osipenko
2021-06-06 22:28 ` [PATCH v1 4/5] clk: tegra: Add stubs needed " Dmitry Osipenko
2021-06-16 19:08   ` Daniel Lezcano
2021-06-16 19:35     ` Dmitry Osipenko
2021-06-06 22:28 ` [PATCH v1 5/5] cpuidle: tegra: Enable " Dmitry Osipenko
2021-06-16  7:37   ` kernel test robot
2021-06-16  7:37     ` kernel test robot
2021-06-16 19:24     ` Dmitry Osipenko
2021-06-16 19:24       ` Dmitry Osipenko
2021-06-16 19:45       ` Dmitry Osipenko [this message]
2021-06-16 19:45         ` 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=4de3f38b-72be-b7d7-a291-0da75dc8455d@gmail.com \
    --to=digetx@gmail.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=jonathanh@nvidia.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=rjw@rjwysocki.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.