* [linux-next:master 5946/11253] mc.c:undefined reference to `reset_controller_register'
@ 2021-06-18 14:42 kernel test robot
2021-06-18 14:56 ` Matthew Wilcox
0 siblings, 1 reply; 3+ messages in thread
From: kernel test robot @ 2021-06-18 14:42 UTC (permalink / raw)
To: Dmitry Osipenko
Cc: kbuild-all, Linux Memory Management List, Thierry Reding,
Krzysztof Kozlowski
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
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-c002-20210618 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=56ebc9b0d77e0406aba2d900c82e79204cc7dc32
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
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD e71e3a48a7e89fa71fb70bf4602367528864d2ff builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
ld: warning: orphan section `.data..decrypted' from `arch/x86/kernel/cpu/vmware.o' being placed in section `.data..decrypted'
ld: warning: orphan section `.data..decrypted' from `arch/x86/kernel/kvm.o' being placed in section `.data..decrypted'
ld: drivers/memory/tegra/mc.o: in function `tegra_mc_probe':
>> mc.c:(.text+0x1efa): undefined reference to `reset_controller_register'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 41729 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-next:master 5946/11253] mc.c:undefined reference to `reset_controller_register'
2021-06-18 14:42 [linux-next:master 5946/11253] mc.c:undefined reference to `reset_controller_register' kernel test robot
@ 2021-06-18 14:56 ` Matthew Wilcox
2021-06-21 9:00 ` [kbuild-all] " Rong Chen
0 siblings, 1 reply; 3+ messages in thread
From: Matthew Wilcox @ 2021-06-18 14:56 UTC (permalink / raw)
To: kernel test robot
Cc: Dmitry Osipenko, kbuild-all, Linux Memory Management List,
Thierry Reding, Krzysztof Kozlowski
On Fri, Jun 18, 2021 at 10:42:13PM +0800, 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-c002-20210618 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=56ebc9b0d77e0406aba2d900c82e79204cc7dc32
> 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
> make W=1 ARCH=x86_64
What is it about this failure that makes the lkp bot think that linux-mm
is an appropriate cc? It seems to get cc'd on all kinds of random bugs,
and I'm never quite sure why.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [kbuild-all] Re: [linux-next:master 5946/11253] mc.c:undefined reference to `reset_controller_register'
2021-06-18 14:56 ` Matthew Wilcox
@ 2021-06-21 9:00 ` Rong Chen
0 siblings, 0 replies; 3+ messages in thread
From: Rong Chen @ 2021-06-21 9:00 UTC (permalink / raw)
To: Matthew Wilcox, kernel test robot
Cc: Dmitry Osipenko, kbuild-all, Linux Memory Management List,
Thierry Reding, Krzysztof Kozlowski
On 6/18/21 10:56 PM, Matthew Wilcox wrote:
> On Fri, Jun 18, 2021 at 10:42:13PM +0800, 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-c002-20210618 (attached as .config)
>> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
>> reproduce (this is a W=1 build):
>> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=56ebc9b0d77e0406aba2d900c82e79204cc7dc32
>> 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
>> make W=1 ARCH=x86_64
> What is it about this failure that makes the lkp bot think that linux-mm
> is an appropriate cc? It seems to get cc'd on all kinds of random bugs,
> and I'm never quite sure why.
>
Hi Matthew,
We hard coded two polices:
1. If Andrew Morton <akpm@linux-foundation.org> involved in the commit,
we will cc linux-mm
2. If the problem repo is linux-next, we will cc linux-mm to archive
these reports for a summary report
(some developers want to read the original report):
https://lore.kernel.org/linux-mm/609ebb8a.MY4vWDkFI93n9l1s%25lkp@intel.com/
Do you want us to adjust the polices?
Best Regards,
Rong Chen
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-06-21 9:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-18 14:42 [linux-next:master 5946/11253] mc.c:undefined reference to `reset_controller_register' kernel test robot
2021-06-18 14:56 ` Matthew Wilcox
2021-06-21 9:00 ` [kbuild-all] " Rong Chen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).