From: kbuild test robot <lkp@intel.com>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Cc: kbuild-all@01.org, broonie@kernel.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] regulator: core: Add debugfs to show constraint flags
Date: Thu, 21 Apr 2016 20:23:50 +0800 [thread overview]
Message-ID: <201604212046.AK7Nfxzu%fengguang.wu@intel.com> (raw)
In-Reply-To: <1461240394-4080-1-git-send-email-rf@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 2621 bytes --]
Hi,
[auto build test ERROR on regulator/for-next]
[also build test ERROR on v4.6-rc4 next-20160420]
[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/Richard-Fitzgerald/regulator-core-Add-debugfs-to-show-constraint-flags/20160421-200958
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
config: powerpc-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=powerpc
All errors (new ones prefixed by >>):
>> drivers/regulator/core.c:1320:10: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.read = constraint_flags_read_file,
^
drivers/regulator/core.c:1320:10: note: (near initialization for 'constraint_flags_fops.read')
drivers/regulator/core.c:2558:1: warning: 'regulator_can_change_voltage' is deprecated [-Wdeprecated-declarations]
EXPORT_SYMBOL_GPL(regulator_can_change_voltage);
^
drivers/regulator/core.c:2541:5: note: declared here
int regulator_can_change_voltage(struct regulator *regulator)
^
In file included from include/linux/linkage.h:6:0,
from include/linux/kernel.h:6,
from drivers/regulator/core.c:16:
include/linux/export.h:63:25: warning: 'regulator_can_change_voltage' is deprecated [-Wdeprecated-declarations]
__visible const struct kernel_symbol __ksymtab_##sym \
^
include/linux/export.h:72:2: note: in expansion of macro '__EXPORT_SYMBOL'
__EXPORT_SYMBOL(sym, "_gpl")
^
drivers/regulator/core.c:2558:1: note: in expansion of macro 'EXPORT_SYMBOL_GPL'
EXPORT_SYMBOL_GPL(regulator_can_change_voltage);
^
drivers/regulator/core.c:2541:5: note: declared here
int regulator_can_change_voltage(struct regulator *regulator)
^
cc1: some warnings being treated as errors
vim +1320 drivers/regulator/core.c
1314
1315 #endif
1316
1317 static const struct file_operations constraint_flags_fops = {
1318 #ifdef CONFIG_DEBUG_FS
1319 .open = simple_open,
> 1320 .read = constraint_flags_read_file,
1321 .llseek = default_llseek,
1322 #endif
1323 };
---
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: 48663 bytes --]
next prev parent reply other threads:[~2016-04-21 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 12:06 Richard Fitzgerald
2016-04-21 12:23 ` kbuild test robot [this message]
2016-04-21 12:30 ` kbuild test robot
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=201604212046.AK7Nfxzu%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=rf@opensource.wolfsonmicro.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®