From: kbuild test robot <lkp@intel.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kbuild-all@01.org, Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH 1/3] stmmac: pci: Overcome stmmac_pci_info structure
Date: Tue, 23 May 2017 21:48:40 +0800 [thread overview]
Message-ID: <201705232106.TbvaiXq7%fengguang.wu@intel.com> (raw)
In-Reply-To: <5d7b7aa99a04e86196ff7eea11f0ede7a95deac1.1495451529.git.jan.kiszka@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]
Hi Jan,
[auto build test ERROR on net-next/master]
[also build test ERROR on v4.12-rc2 next-20170523]
[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/Jan-Kiszka/stmmac-pci-Refactor-DMI-probing/20170523-165305
config: x86_64-allmodconfig (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/net/ethernet/stmicro/stmmac/stmmac_pci.c:267:3: error: initializer element is not computable at load time
(kernel_ulong_t)&stmmac_default_setup,
^
drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:267:3: note: (near initialization for 'stmmac_id_table[0].class')
drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:271:3: error: initializer element is not computable at load time
(kernel_ulong_t)&stmmac_default_setup,
^
drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:271:3: note: (near initialization for 'stmmac_id_table[1].class')
vim +267 drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c
261 #define STMMAC_QUARK_ID 0x0937
262 #define STMMAC_DEVICE_ID 0x1108
263
264 static const struct pci_device_id stmmac_id_table[] = {
265 {
266 PCI_DEVICE(STMMAC_VENDOR_ID, STMMAC_DEVICE_ID),
> 267 (kernel_ulong_t)&stmmac_default_setup,
268 },
269 {
270 PCI_DEVICE(PCI_VENDOR_ID_STMICRO, PCI_DEVICE_ID_STMICRO_MAC),
---
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: 60065 bytes --]
next prev parent reply other threads:[~2017-05-23 13:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 11:12 [PATCH 0/3] stmmac: pci: Refactor DMI probing Jan Kiszka
2017-05-22 11:12 ` [PATCH 1/3] stmmac: pci: Overcome stmmac_pci_info structure Jan Kiszka
2017-05-22 17:09 ` Andy Shevchenko
2017-05-23 13:48 ` kbuild test robot [this message]
2017-05-22 11:12 ` [PATCH 2/3] stmmac: pci: Make stmmac_pci_find_phy_addr truly generic Jan Kiszka
2017-05-22 11:12 ` [PATCH 3/3] stmmac: pci: Use dmi_system_id table for retrieving PHY addresses Jan Kiszka
2017-05-22 11:33 ` Joe Perches
2017-05-22 12:49 ` Jan Kiszka
2017-05-22 13:13 ` Joe Perches
2017-05-22 16:59 ` Andy Shevchenko
2017-05-22 16:35 ` [PATCH 0/3] stmmac: pci: Refactor DMI probing David Miller
2017-05-22 17:06 ` Jan Kiszka
2017-05-22 18:23 ` David Miller
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=201705232106.TbvaiXq7%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alexandre.torgue@st.com \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=jan.kiszka@siemens.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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®