From: kbuild test robot <lkp@intel.com>
To: Simon Que <sque@chromium.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ben Chan <benchan@chromium.org>,
Chun-Ta Lin <itspeter@chromium.org>,
Zhongze Hu <frankhu@chromium.org>, Joe Perches <joe@perches.com>,
Simon Que <sque@chromium.org>,
Rob Springer <rspringer@google.com>,
John Joseph <jnjoseph@google.com>
Subject: Re: [PATCH v6] drivers/staging: Gasket driver framework + Apex driver
Date: Sat, 30 Jun 2018 13:32:02 +0800 [thread overview]
Message-ID: <201806301328.BOTLFqrH%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180630000253.70103-1-sque@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 5725 bytes --]
Hi Simon,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.18-rc2 next-20180629]
[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/Simon-Que/drivers-staging-Gasket-driver-framework-Apex-driver/20180630-080504
config: i386-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from drivers/staging/gasket/gasket_core.c:16:0:
drivers/staging/gasket/gasket_core.h: In function 'gasket_dev_read_64':
>> drivers/staging/gasket/gasket_core.h:658:9: error: implicit declaration of function 'readq'; did you mean 'readl'? [-Werror=implicit-function-declaration]
return readq(&gasket_dev->bar_data[bar].virt_base[location]);
^~~~~
readl
drivers/staging/gasket/gasket_core.h: In function 'gasket_dev_write_64':
drivers/staging/gasket/gasket_core.h:664:2: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
writeq(value, &dev->bar_data[bar].virt_base[location]);
^~~~~~
writel
cc1: some warnings being treated as errors
--
In file included from drivers/staging/gasket/gasket_ioctl.h:15:0,
from drivers/staging/gasket/gasket_ioctl.c:13:
drivers/staging/gasket/gasket_core.h: In function 'gasket_dev_read_64':
>> drivers/staging/gasket/gasket_core.h:658:9: error: implicit declaration of function 'readq'; did you mean 'readl'? [-Werror=implicit-function-declaration]
return readq(&gasket_dev->bar_data[bar].virt_base[location]);
^~~~~
readl
drivers/staging/gasket/gasket_core.h: In function 'gasket_dev_write_64':
drivers/staging/gasket/gasket_core.h:664:2: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
writeq(value, &dev->bar_data[bar].virt_base[location]);
^~~~~~
writel
drivers/staging/gasket/gasket_ioctl.c: In function 'gasket_config_coherent_allocator':
drivers/staging/gasket/gasket_ioctl.c:442:27: error: passing argument 3 of 'gasket_alloc_coherent_memory' from incompatible pointer type [-Werror=incompatible-pointer-types]
gasket_dev, ibuf.size, &ibuf.dma_address,
^
In file included from drivers/staging/gasket/gasket_ioctl.c:18:0:
drivers/staging/gasket/gasket_page_table.h:240:5: note: expected 'dma_addr_t * {aka unsigned int *}' but argument is of type 'u64 * {aka long long unsigned int *}'
int gasket_alloc_coherent_memory(struct gasket_dev *gasket_dev, uint64_t size,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
--
In file included from drivers/staging/gasket/gasket_page_table.h:26:0,
from drivers/staging/gasket/gasket_page_table.c:41:
drivers/staging/gasket/gasket_core.h: In function 'gasket_dev_read_64':
>> drivers/staging/gasket/gasket_core.h:658:9: error: implicit declaration of function 'readq'; did you mean 'readl'? [-Werror=implicit-function-declaration]
return readq(&gasket_dev->bar_data[bar].virt_base[location]);
^~~~~
readl
drivers/staging/gasket/gasket_core.h: In function 'gasket_dev_write_64':
drivers/staging/gasket/gasket_core.h:664:2: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
writeq(value, &dev->bar_data[bar].virt_base[location]);
^~~~~~
writel
drivers/staging/gasket/gasket_page_table.c: In function 'gasket_is_extended_dev_addr_bad':
drivers/staging/gasket/gasket_page_table.c:1388:11: warning: right shift count >= width of type [-Wshift-count-overflow]
if (addr >> (GASKET_EXTENDED_LVL0_WIDTH + GASKET_EXTENDED_LVL0_SHIFT)) {
^~
drivers/staging/gasket/gasket_page_table.c: In function 'gasket_alloc_coherent_memory':
drivers/staging/gasket/gasket_page_table.c:1694:4: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
(u64)mem + j * PAGE_SIZE;
^
cc1: some warnings being treated as errors
vim +658 drivers/staging/gasket/gasket_core.h
627
628 /*
629 * Memory management functions. These will likely be spun off into their own
630 * file in the future.
631 */
632
633 /* Unmaps the specified mappable region from a VMA. */
634 int gasket_mm_unmap_region(
635 const struct gasket_dev *gasket_dev, struct vm_area_struct *vma,
636 const struct gasket_mappable_region *map_region);
637
638 /*
639 * Get the ioctl permissions callback.
640 * @gasket_dev: Gasket device structure.
641 */
642 gasket_ioctl_permissions_cb_t gasket_get_ioctl_permissions_cb(
643 struct gasket_dev *gasket_dev);
644
645 /**
646 * Lookup a name by number in a num_name table.
647 * @num: Number to lookup.
648 * @table: Array of num_name structures, the table for the lookup.
649 *
650 */
651 const char *gasket_num_name_lookup(
652 uint num, const struct gasket_num_name *table);
653
654 /* Handy inlines */
655 static inline ulong gasket_dev_read_64(
656 struct gasket_dev *gasket_dev, int bar, ulong location)
657 {
> 658 return readq(&gasket_dev->bar_data[bar].virt_base[location]);
659 }
660
---
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: 64159 bytes --]
prev parent reply other threads:[~2018-06-30 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 0:02 Simon Que
2018-06-30 0:17 ` Randy Dunlap
2018-06-30 5:32 ` kbuild test robot [this message]
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=201806301328.BOTLFqrH%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=benchan@chromium.org \
--cc=frankhu@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=itspeter@chromium.org \
--cc=jnjoseph@google.com \
--cc=joe@perches.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rspringer@google.com \
--cc=sque@chromium.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
all inboxes | Powered by JetHome®