From: lkp@intel.com (kbuild test robot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v2] bus: mvebu-mbus: Provide stub function for mvebu_mbus_get_io_win_info()
Date: Thu, 1 Sep 2016 19:31:45 +0800 [thread overview]
Message-ID: <201609011930.BQGnLcb2%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160901093904.26564-1-sr@denx.de>
Hi Stefan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.8-rc4 next-20160825]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Stefan-Roese/bus-mvebu-mbus-Provide-stub-function-for-mvebu_mbus_get_io_win_info/20160901-174432
config: arm64-defconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 5.4.0-6) 5.4.0 20160609
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm64
All errors (new ones prefixed by >>):
In file included from drivers/ata/ahci_mvebu.c:16:0:
include/linux/mbus.h: In function 'mvebu_mbus_get_io_win_info':
>> include/linux/mbus.h:79:10: error: 'EINVAL' undeclared (first use in this function)
return -EINVAL;
^
include/linux/mbus.h:79:10: note: each undeclared identifier is reported only once for each function it appears in
vim +/EINVAL +79 include/linux/mbus.h
73 * On all ARM32 MVEBU platforms with MBus support, this stub
74 * function will not get called. The real function from the
75 * MBus driver is called instead. ARM64 MVEBU platforms like
76 * the Armada 3700 could do use the mv_xor device which calls
77 * into this function
78 */
> 79 return -EINVAL;
80 }
81 #endif
82
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/octet-stream
Size: 30700 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160901/3de94e7f/attachment-0001.obj>
next prev parent reply other threads:[~2016-09-01 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 9:39 [PATCH 1/2 v2] bus: mvebu-mbus: Provide stub function for mvebu_mbus_get_io_win_info() Stefan Roese
2016-09-01 9:39 ` [PATCH 2/2 v4] dmaengine: mv_xor: Add support for IO (PCIe) src/dst areas Stefan Roese
2016-09-01 11:31 ` kbuild test robot [this message]
2016-09-01 12:23 ` [PATCH 1/2 v2] bus: mvebu-mbus: Provide stub function for mvebu_mbus_get_io_win_info() Andrew Lunn
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=201609011930.BQGnLcb2%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.