From: kbuild test robot <lkp@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: kbuild-all@lists.01.org, linux-edac@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-efi@vger.kernel.org,
Borislav Petkov <bp@alien8.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
james.morse@arm.com, rjw@rjwysocki.net, tony.luck@intel.com,
linuxarm@huawei.com, ard.biesheuvel@linaro.org,
nariman.poushin@linaro.org,
Thanu Rangarajan <Thanu.Rangarajan@arm.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v3 2/6] efi / ras: CCIX Cache error reporting
Date: Wed, 13 Nov 2019 17:32:55 +0800 [thread overview]
Message-ID: <201911131729.a46FsZJv%lkp@intel.com> (raw)
In-Reply-To: <20191112165226.106107-3-Jonathan.Cameron@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2277 bytes --]
Hi Jonathan,
I love your patch! Yet something to improve:
[auto build test ERROR on efi/next]
[also build test ERROR on v5.4-rc7 next-20191112]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Jonathan-Cameron/efi-ras-CCIX-Memory-error-reporting/20191113-133322
base: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next
config: i386-defconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: drivers/ras/ras.o: in function `perf_trace_ccix_memory_error_event':
ras.c:(.text+0x794): undefined reference to `cper_ccix_mem_err_pack'
ld: drivers/ras/ras.o: in function `trace_raw_output_ccix_memory_error_event':
ras.c:(.text+0x83d): undefined reference to `cper_ccix_mem_err_unpack'
ld: ras.c:(.text+0x863): undefined reference to `cper_ccix_comp_type_str'
ld: ras.c:(.text+0x86f): undefined reference to `cper_severity_str'
ld: drivers/ras/ras.o: in function `perf_trace_ccix_cache_error_event':
>> ras.c:(.text+0x9f4): undefined reference to `cper_ccix_cache_err_pack'
ld: drivers/ras/ras.o: in function `trace_raw_output_ccix_cache_error_event':
>> ras.c:(.text+0xa9d): undefined reference to `cper_ccix_cache_err_unpack'
ld: ras.c:(.text+0xac3): undefined reference to `cper_ccix_comp_type_str'
ld: ras.c:(.text+0xacf): undefined reference to `cper_severity_str'
ld: drivers/ras/ras.o: in function `trace_event_raw_event_ccix_memory_error_event':
ras.c:(.text+0x1349): undefined reference to `cper_ccix_mem_err_pack'
ld: drivers/ras/ras.o: in function `trace_event_raw_event_ccix_cache_error_event':
ras.c:(.text+0x14b9): undefined reference to `cper_ccix_cache_err_pack'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28148 bytes --]
next prev parent reply other threads:[~2019-11-13 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 16:52 [PATCH v3 0/6] CCIX Protocol error reporting Jonathan Cameron
2019-11-12 16:52 ` [PATCH v3 1/6] efi / ras: CCIX Memory " Jonathan Cameron
2019-11-13 6:43 ` kbuild test robot
2019-11-13 8:20 ` kbuild test robot
2019-11-12 16:52 ` [PATCH v3 2/6] efi / ras: CCIX Cache " Jonathan Cameron
2019-11-13 9:10 ` kbuild test robot
2019-11-13 9:32 ` kbuild test robot [this message]
2019-11-12 16:52 ` [PATCH v3 3/6] efi / ras: CCIX Address Translation " Jonathan Cameron
2019-11-13 9:55 ` kbuild test robot
2019-11-12 16:52 ` [PATCH v3 4/6] efi / ras: CCIX Port " Jonathan Cameron
2019-11-12 16:52 ` [PATCH v3 5/6] efi / ras: CCIX Link " Jonathan Cameron
2019-11-12 16:52 ` [PATCH v3 6/6] efi / ras: CCIX Agent internal " Jonathan Cameron
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=201911131729.a46FsZJv%lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Thanu.Rangarajan@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mchehab@kernel.org \
--cc=nariman.poushin@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).