From: kbuild test robot <lkp@intel.com>
To: Or Idgar <idgar@virtualoco.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, arnd@arndb.de, ghammer@redhat.com,
Or Idgar <oridgar@gmail.com>
Subject: Re: [PATCH] drivers/virt: vm_gen_counter: initial driver implementation
Date: Sat, 24 Feb 2018 17:06:47 +0800 [thread overview]
Message-ID: <201802241726.nuC5WB8Z%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180222162038.28768-1-idgar@virtualoco.com>
Hi Or,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on v4.16-rc2 next-20180223]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Or-Idgar/drivers-virt-vm_gen_counter-initial-driver-implementation/20180224-112017
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/misc/vmgenid.c:35:15: sparse: incorrect type in assignment (different address spaces) @@ expected struct uuid_t @@ got uct uuid_t @@
drivers/misc/vmgenid.c:35:15: expected struct uuid_t
drivers/misc/vmgenid.c:35:15: got void
>> drivers/misc/vmgenid.c:40:29: sparse: incorrect type in argument 1 (different address spaces) @@ expected void @@ got strvoid @@
drivers/misc/vmgenid.c:40:29: expected void
drivers/misc/vmgenid.c:40:29: got struct uuid_t
drivers/misc/vmgenid.c:51:15: sparse: incorrect type in assignment (different address spaces) @@ expected struct uuid_t @@ got uct uuid_t @@
drivers/misc/vmgenid.c:51:15: expected struct uuid_t
drivers/misc/vmgenid.c:51:15: got void
drivers/misc/vmgenid.c:55:29: sparse: incorrect type in argument 1 (different address spaces) @@ expected void @@ got strvoid @@
drivers/misc/vmgenid.c:55:29: expected void
drivers/misc/vmgenid.c:55:29: got struct uuid_t
vim +35 drivers/misc/vmgenid.c
28
29 static ssize_t generation_id_show(struct device *_d,
30 struct device_attribute *attr, char *buf)
31 {
32 uuid_t *uuidp;
33 ssize_t result;
34
> 35 uuidp = acpi_os_map_iomem(phy_addr, sizeof(uuid_t));
36 if (!uuidp)
37 return -EFAULT;
38
39 result = sprintf(buf, "%pUl\n", uuidp);
> 40 acpi_os_unmap_iomem(uuidp, sizeof(uuid_t));
41 return result;
42 }
43 static DEVICE_ATTR_RO(generation_id);
44
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-02-24 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 16:20 Or Idgar
2018-02-22 16:36 ` Greg KH
2018-02-22 16:49 ` Gal Hammer
2018-02-24 5:10 ` kbuild test robot
2018-02-24 9:06 ` kbuild test robot [this message]
2018-02-24 9:42 ` kbuild test robot
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=201802241726.nuC5WB8Z%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=ghammer@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=idgar@virtualoco.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oridgar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®