From: kbuild test robot <lkp@intel.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: kbuild-all@01.org, Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: Re: [PATCH 1/2] mfd: lm3533: fix build warning
Date: Wed, 7 Oct 2015 20:41:35 +0800 [thread overview]
Message-ID: <201510072053.nsKY3CK0%fengguang.wu@intel.com> (raw)
In-Reply-To: <1444220929-18949-1-git-send-email-sudipm.mukherjee@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]
Hi Sudip,
[auto build test ERROR on v4.3-rc4 -- if it's inappropriate base, please ignore]
config: x86_64-randconfig-x002-201540 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/mfd/lm3533-core.c: In function 'lm3533_i2c_probe':
>> drivers/mfd/lm3533-core.c:615:2: error: 'ret' undeclared (first use in this function)
ret = lm3533_device_init(lm3533);
^
drivers/mfd/lm3533-core.c:615:2: note: each undeclared identifier is reported only once for each function it appears in
vim +/ret +615 drivers/mfd/lm3533-core.c
fa648e51 Johan Hovold 2012-05-15 609 if (IS_ERR(lm3533->regmap))
fa648e51 Johan Hovold 2012-05-15 610 return PTR_ERR(lm3533->regmap);
16c5c023 Johan Hovold 2012-05-03 611
16c5c023 Johan Hovold 2012-05-03 612 lm3533->dev = &i2c->dev;
16c5c023 Johan Hovold 2012-05-03 613 lm3533->irq = i2c->irq;
16c5c023 Johan Hovold 2012-05-03 614
16c5c023 Johan Hovold 2012-05-03 @615 ret = lm3533_device_init(lm3533);
16c5c023 Johan Hovold 2012-05-03 616 if (ret)
fa648e51 Johan Hovold 2012-05-15 617 return ret;
16c5c023 Johan Hovold 2012-05-03 618
:::::: The code at line 615 was first introduced by commit
:::::: 16c5c023aac86228e3e94c4bf6d19708ea861a05 mfd: Add LM3533 lighting-power core driver
:::::: TO: Johan Hovold <jhovold@gmail.com>
:::::: CC: Samuel Ortiz <sameo@linux.intel.com>
---
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: 22104 bytes --]
next prev parent reply other threads:[~2015-10-07 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 12:28 Sudip Mukherjee
2015-10-07 12:28 ` [PATCH 2/2] mfd: rtsx: " Sudip Mukherjee
2015-10-07 12:40 ` kbuild test robot
2015-10-07 12:46 ` Sudip Mukherjee
2015-10-07 13:48 ` [kbuild-all] " Fengguang Wu
2015-10-07 15:41 ` Sudip Mukherjee
2015-10-08 0:56 ` Fengguang Wu
2015-10-08 6:30 ` Greg KH
2015-10-08 7:45 ` Sudip Mukherjee
2015-10-13 8:45 ` Lee Jones
2015-10-07 12:41 ` kbuild test robot [this message]
2015-10-13 8:45 ` [PATCH 1/2] mfd: lm3533: " Lee Jones
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=201510072053.nsKY3CK0%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@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®