From: kbuild test robot <lkp@intel.com>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: kbuild-all@01.org, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Brian Norris <briannorris@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [PATCH v2] regulator: core: Limit propagation of parent voltage count and list
Date: Tue, 28 Mar 2017 12:20:42 +0800 [thread overview]
Message-ID: <201703281258.Trc7L3Cb%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170327212247.92317-1-mka@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]
Hi Matthias,
[auto build test WARNING on regulator/for-next]
[also build test WARNING on v4.11-rc4 next-20170327]
[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/Matthias-Kaehlcke/regulator-core-Limit-propagation-of-parent-voltage-count-and-list/20170328-095816
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
config: x86_64-randconfig-s0-03281146 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
drivers//regulator/core.c: In function 'regulator_count_voltages':
>> drivers//regulator/core.c:2543: warning: unused variable 'ops'
vim +/ops +2543 drivers//regulator/core.c
2527
2528 return ret;
2529 }
2530 EXPORT_SYMBOL_GPL(regulator_is_enabled);
2531
2532 /**
2533 * regulator_count_voltages - count regulator_list_voltage() selectors
2534 * @regulator: regulator source
2535 *
2536 * Returns number of selectors, or negative errno. Selectors are
2537 * numbered starting at zero, and typically correspond to bitfields
2538 * in hardware registers.
2539 */
2540 int regulator_count_voltages(struct regulator *regulator)
2541 {
2542 struct regulator_dev *rdev = regulator->rdev;
> 2543 const struct regulator_ops *ops = rdev->desc->ops;
2544
2545 if (rdev->desc->n_voltages)
2546 return rdev->desc->n_voltages;
2547
2548 if (!rdev->is_switch || !rdev->supply)
2549 return -EINVAL;
2550
2551 return regulator_count_voltages(rdev->supply);
---
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: 22079 bytes --]
prev parent reply other threads:[~2017-03-28 4:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 21:22 Matthias Kaehlcke
2017-03-28 4:20 ` kbuild test robot [this message]
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=201703281258.Trc7L3Cb%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=javier@osg.samsung.com \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.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®