From: kbuild test robot <fengguang.wu@intel.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: kbuild-all@01.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
Gabriel Somlo <somlo@cmu.edu>
Subject: [vhost:vhost 11/22] drivers//firmware/qemu_fw_cfg.c:380:3: error: implicit declaration of function 'paddr_vmcoreinfo_note'
Date: Thu, 1 Feb 2018 17:47:53 +0800 [thread overview]
Message-ID: <201802011750.UXhfgECe%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3695 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost
head: 9991b95cb712cdd9a40240bde6274d5415476fb5
commit: 860c7fa9d6d433011e82a4f7f896893e914ce4a9 [11/22] fw_cfg: write vmcoreinfo details
config: i386-randconfig-a0-201804 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
git checkout 860c7fa9d6d433011e82a4f7f896893e914ce4a9
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from include/linux/byteorder/little_endian.h:5:0,
from arch/x86/include/uapi/asm/byteorder.h:5,
from include/asm-generic/bitops/le.h:6,
from arch/x86/include/asm/bitops.h:518,
from include/linux/bitops.h:38,
from include/linux/kernel.h:11,
from include/linux/list.h:9,
from include/linux/module.h:9,
from drivers//firmware/qemu_fw_cfg.c:30:
drivers//firmware/qemu_fw_cfg.c: In function 'write_vmcoreinfo':
drivers//firmware/qemu_fw_cfg.c:379:23: error: 'VMCOREINFO_NOTE_SIZE' undeclared (first use in this function)
.size = cpu_to_le32(VMCOREINFO_NOTE_SIZE),
^
include/uapi/linux/byteorder/little_endian.h:33:51: note: in definition of macro '__cpu_to_le32'
#define __cpu_to_le32(x) ((__force __le32)(__u32)(x))
^
drivers//firmware/qemu_fw_cfg.c:379:11: note: in expansion of macro 'cpu_to_le32'
.size = cpu_to_le32(VMCOREINFO_NOTE_SIZE),
^
drivers//firmware/qemu_fw_cfg.c:379:23: note: each undeclared identifier is reported only once for each function it appears in
.size = cpu_to_le32(VMCOREINFO_NOTE_SIZE),
^
include/uapi/linux/byteorder/little_endian.h:33:51: note: in definition of macro '__cpu_to_le32'
#define __cpu_to_le32(x) ((__force __le32)(__u32)(x))
^
drivers//firmware/qemu_fw_cfg.c:379:11: note: in expansion of macro 'cpu_to_le32'
.size = cpu_to_le32(VMCOREINFO_NOTE_SIZE),
^
>> drivers//firmware/qemu_fw_cfg.c:380:3: error: implicit declaration of function 'paddr_vmcoreinfo_note' [-Werror=implicit-function-declaration]
.paddr = cpu_to_le64(paddr_vmcoreinfo_note())
^
cc1: some warnings being treated as errors
vim +/paddr_vmcoreinfo_note +380 drivers//firmware/qemu_fw_cfg.c
360
361 #ifdef CONFIG_CRASH_CORE
362 static ssize_t write_vmcoreinfo(struct device *dev, const struct fw_cfg_file *f)
363 {
364 struct vmci {
365 __le16 host_format;
366 __le16 guest_format;
367 __le32 size;
368 __le64 paddr;
369 } __packed;
370 static struct vmci *data;
371 ssize_t ret;
372
373 data = kmalloc(sizeof(struct vmci), GFP_KERNEL);
374 if (!data)
375 return -ENOMEM;
376
377 *data = (struct vmci) {
378 .guest_format = cpu_to_le16(VMCOREINFO_FORMAT_ELF),
> 379 .size = cpu_to_le32(VMCOREINFO_NOTE_SIZE),
> 380 .paddr = cpu_to_le64(paddr_vmcoreinfo_note())
381 };
382 /* spare ourself reading host format support for now since we
383 * don't know what else to format - host may ignore ours
384 */
385 ret = fw_cfg_write_blob(dev, f->select, data, 0, sizeof(struct vmci));
386
387 kfree(data);
388 return ret;
389 }
390 #endif /* CONFIG_CRASH_CORE */
391
---
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: 28150 bytes --]
reply other threads:[~2018-02-01 9:47 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=201802011750.UXhfgECe%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=somlo@cmu.edu \
--cc=virtualization@lists.linux-foundation.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).