From: kbuild test robot <lkp@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: kbuild-all@01.org, linux-efi@vger.kernel.org
Subject: [efi:next 2/3] arch/x86/platform/efi/efi.c:77:3: error: 'uv_systab_phys' undeclared here (not in a function); did you mean 'uv_system_init'?
Date: Tue, 2 Jul 2019 17:55:47 +0800 [thread overview]
Message-ID: <201907021746.8EVozoqp%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/efi/efi.git next
head: 2af9ef2e77c10897c5767b42e7bc09ac387af947
commit: a2b67b33dee5c8c4b9933ecc04e48755a3a87cae [2/3] efi/x86: move UV_SYSTAB handling into arch/x86
config: i386-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-9) 7.4.0
reproduce:
git checkout a2b67b33dee5c8c4b9933ecc04e48755a3a87cae
# 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 >>):
>> arch/x86/platform/efi/efi.c:77:3: error: 'uv_systab_phys' undeclared here (not in a function); did you mean 'uv_system_init'?
&uv_systab_phys,
^~~~~~~~~~~~~~
uv_system_init
vim +77 arch/x86/platform/efi/efi.c
66
67 static const unsigned long * const efi_tables[] = {
68 &efi.mps,
69 &efi.acpi,
70 &efi.acpi20,
71 &efi.smbios,
72 &efi.smbios3,
73 &efi.sal_systab,
74 &efi.boot_info,
75 &efi.hcdp,
76 &efi.uga,
> 77 &uv_systab_phys,
78 &efi.fw_vendor,
79 &efi.runtime,
80 &efi.config_table,
81 &efi.esrt,
82 &efi.properties_table,
83 &efi.mem_attr_table,
84 };
85
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 68861 bytes --]
reply other threads:[~2019-07-02 9:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201907021746.8EVozoqp%lkp@intel.com \
--to=lkp@intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=kbuild-all@01.org \
--cc=linux-efi@vger.kernel.org \
/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).