From: kbuild test robot <lkp@intel.com>
To: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
Cc: kbuild-all@01.org, sre@kernel.org, dbaryshkov@gmail.com,
dwmw2@infradead.org, pali.rohar@gmail.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
Subject: Re: [PATCH v1] power: bq27xxx_battery: Restore device name
Date: Tue, 2 Feb 2016 20:47:52 +0800 [thread overview]
Message-ID: <201602022011.2El0Byf5%fengguang.wu@intel.com> (raw)
In-Reply-To: <1454416458-2541-1-git-send-email-ivo.g.dimitrov.75@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
Hi Ivaylo,
[auto build test ERROR on battery/master]
[also build test ERROR on v4.5-rc2 next-20160201]
[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/Ivaylo-Dimitrov/power-bq27xxx_battery-Restore-device-name/20160202-203646
base: git://git.infradead.org/battery-2.6.git master
config: i386-randconfig-x003-02010231 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/power/bq27xxx_battery_i2c.c: In function 'bq27xxx_battery_i2c_remove':
>> drivers/power/bq27xxx_battery_i2c.c:141:26: error: 'num' undeclared (first use in this function)
idr_remove(&battery_id, num);
^
drivers/power/bq27xxx_battery_i2c.c:141:26: note: each undeclared identifier is reported only once for each function it appears in
vim +/num +141 drivers/power/bq27xxx_battery_i2c.c
135 {
136 struct bq27xxx_device_info *di = i2c_get_clientdata(client);
137
138 bq27xxx_battery_teardown(di);
139
140 mutex_lock(&battery_mutex);
> 141 idr_remove(&battery_id, num);
142 mutex_unlock(&battery_mutex);
143
144 return 0;
---
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: 21507 bytes --]
next prev parent reply other threads:[~2016-02-02 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 12:15 [PATCH] " Ivaylo Dimitrov
2016-02-02 12:27 ` Pali Rohár
2016-02-02 12:32 ` Ivaylo Dimitrov
2016-02-02 12:34 ` [PATCH v1] " Ivaylo Dimitrov
2016-02-02 12:37 ` Ivaylo Dimitrov
2016-02-02 12:47 ` [PATCH v2] " Ivaylo Dimitrov
2016-02-06 10:35 ` Pali Rohár
2016-02-21 11:34 ` Pali Rohár
2016-02-23 9:32 ` Pali Rohár
2016-02-02 12:47 ` kbuild test robot [this message]
2016-02-02 12:27 ` [PATCH] " Ivaylo Dimitrov
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=201602022011.2El0Byf5%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=sre@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®