From: kbuild test robot <lkp@intel.com>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
devel@driverdev.osuosl.org, charrer@alacritech.com,
linux-kernel@vger.kernel.org, liodot@gmail.com
Subject: Re: [PATCH] staging: slicoss: fix different address space warnings
Date: Wed, 16 Nov 2016 05:06:15 +0800 [thread overview]
Message-ID: <201611160558.LogvJ6pn%fengguang.wu@intel.com> (raw)
In-Reply-To: <1479230377-22861-1-git-send-email-sergio.paracuellos@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
Hi Sergio,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.9-rc5 next-20161115]
[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/Sergio-Paracuellos/staging-slicoss-fix-different-address-space-warnings/20161116-025006
config: x86_64-acpi-redef (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `slic_upr_request_complete':
>> slicoss.c:(.text+0x6830c7): undefined reference to `ioread64'
slicoss.c:(.text+0x6830e4): undefined reference to `ioread64'
slicoss.c:(.text+0x683102): undefined reference to `ioread64'
slicoss.c:(.text+0x683120): undefined reference to `ioread64'
slicoss.c:(.text+0x68313e): undefined reference to `ioread64'
drivers/built-in.o:slicoss.c:(.text+0x68315c): more undefined references to `ioread64' follow
---
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: 28638 bytes --]
next prev parent reply other threads:[~2016-11-15 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 17:19 Sergio Paracuellos
2016-11-15 18:22 ` Greg KH
2016-11-15 19:11 ` kbuild test robot
2016-11-15 21:06 ` kbuild test robot [this message]
2016-11-16 10:34 ` Dan Carpenter
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=201611160558.LogvJ6pn%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=charrer@alacritech.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liodot@gmail.com \
--cc=sergio.paracuellos@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®