From: kbuild test robot <lkp@intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: kbuild-all@01.org, Johannes Thumshirn <jthumshirn@suse.de>,
Andreas Werner <andreas.werner@men.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mcb: Correctly initialize the bus's device
Date: Fri, 18 Mar 2016 22:04:04 +0800 [thread overview]
Message-ID: <201603182254.062q7q5B%fengguang.wu@intel.com> (raw)
In-Reply-To: <1458308992-5953-2-git-send-email-jthumshirn@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
Hi Johannes,
[auto build test ERROR on v4.5-rc7]
[also build test ERROR on next-20160318]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Johannes-Thumshirn/mcb-export-FPGA-information-via-sysfs/20160318-215254
config: x86_64-randconfig-x001-201611 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the linux-review/Johannes-Thumshirn/mcb-export-FPGA-information-via-sysfs/20160318-215254 HEAD c6d1aabc2067586d00c2b367c36e8b0df9a151ce builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
drivers/mcb/mcb-core.c: In function 'mcb_alloc_bus':
>> drivers/mcb/mcb-core.c:208:19: error: 'mcb_carrier_device_type' undeclared (first use in this function)
bus->dev.type = &mcb_carrier_device_type;
^
drivers/mcb/mcb-core.c:208:19: note: each undeclared identifier is reported only once for each function it appears in
vim +/mcb_carrier_device_type +208 drivers/mcb/mcb-core.c
202 bus->bus_nr = bus_nr;
203 bus->carrier = carrier;
204
205 device_initialize(&bus->dev);
206 bus->dev.parent = carrier;
207 bus->dev.bus = &mcb_bus_type;
> 208 bus->dev.type = &mcb_carrier_device_type;
209
210 dev_set_name(&bus->dev, "mcb:%d", bus_nr);
211 rc = device_add(&bus->dev);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 19137 bytes --]
next prev parent reply other threads:[~2016-03-18 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 13:49 [PATCH 0/2] mcb: export FPGA information via sysfs Johannes Thumshirn
2016-03-18 13:49 ` [PATCH 1/2] mcb: Correctly initialize the bus's device Johannes Thumshirn
2016-03-18 14:04 ` kbuild test robot [this message]
2016-03-18 13:49 ` [PATCH 2/2] mcb: export bus information via sysfs Johannes Thumshirn
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=201603182254.062q7q5B%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=andreas.werner@men.de \
--cc=jthumshirn@suse.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.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®