From: kbuild test robot <lkp-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kbuild-all-JC7UmRfGjtg@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org,
shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
stefan-XLVq0VzYD2Y@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Sanchayan Maity
<maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v4 4/5] soc: Add SoC driver for Freescale Vybrid platform
Date: Fri, 8 Jul 2016 06:25:21 +0800 [thread overview]
Message-ID: <201607080608.ppfp0BMi%fengguang.wu@intel.com> (raw)
In-Reply-To: <f600ac1c747813b26c80149b6fdf32d42b114235.1467872014.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2123 bytes --]
Hi,
[auto build test ERROR on shawnguo/for-next]
[also build test ERROR on v4.7-rc6]
[cannot apply to next-20160707]
[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/Sanchayan-Maity/Implement-SoC-driver-for-Vybrid/20160707-145122
base: https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git for-next
config: arm-arm67 (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 5.3.1-8) 5.3.1 20160205
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=arm
All error/warnings (new ones prefixed by >>):
drivers/soc/fsl/soc-vf610.c: In function 'vf610_soc_probe':
>> drivers/soc/fsl/soc-vf610.c:73:21: error: implicit declaration of function 'of_nvmem_cell_get_direct' [-Werror=implicit-function-declaration]
info->ocotp_cfg0 = of_nvmem_cell_get_direct(cfg0_node);
^
>> drivers/soc/fsl/soc-vf610.c:73:19: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
info->ocotp_cfg0 = of_nvmem_cell_get_direct(cfg0_node);
^
drivers/soc/fsl/soc-vf610.c:79:19: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
info->ocotp_cfg1 = of_nvmem_cell_get_direct(cfg1_node);
^
cc1: some warnings being treated as errors
vim +/of_nvmem_cell_get_direct +73 drivers/soc/fsl/soc-vf610.c
67 cfg1_node = of_find_node_by_name(soc_node, "cfg1");
68 if (!cfg1_node) {
69 ret = -ENODEV;
70 goto out_cfg1_node;
71 }
72
> 73 info->ocotp_cfg0 = of_nvmem_cell_get_direct(cfg0_node);
74 if (IS_ERR(info->ocotp_cfg0)) {
75 ret = PTR_ERR(info->ocotp_cfg0);
76 goto out_ocotp_cfg0;
---
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: 29428 bytes --]
next prev parent reply other threads:[~2016-07-07 22:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 6:39 [PATCH v4 0/5] Implement SoC driver for Vybrid Sanchayan Maity
2016-07-07 6:39 ` [PATCH v4 1/5] ARM: dts: vfxxx: Add device tree node for OCOTP Sanchayan Maity
2016-07-07 6:39 ` [PATCH v4 2/5] ARM: dts: vfxxx: Add On-Chip ROM node for Vybrid Sanchayan Maity
[not found] ` <cover.1467872014.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-07 6:39 ` [PATCH v4 3/5] nvmem: core: Add consumer API to get nvmem cell from node Sanchayan Maity
[not found] ` <0e6294d931bf181376a6f4e1a86df3f6c6a5d575.1467872014.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-07 9:18 ` Srinivas Kandagatla
[not found] ` <577E1E79.4090809-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-07-07 12:33 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-07-07 13:16 ` Srinivas Kandagatla
[not found] ` <577E5634.7020805-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-07-07 13:48 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <20160707134811.GA2692-2b/appYahYDPUjlVagVGR1Kr0EmMEXJSn9A1Ff6Mc9Q@public.gmane.org>
2016-07-08 15:41 ` Srinivas Kandagatla
[not found] ` <577FC9BA.2020402-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-07-08 16:42 ` Stefan Agner
2016-07-08 17:23 ` Srinivas Kandagatla
2016-07-14 5:28 ` Stefan Agner
[not found] ` <577FE19E.4000100-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-08-02 5:34 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-07-07 6:39 ` [PATCH v4 4/5] soc: Add SoC driver for Freescale Vybrid platform Sanchayan Maity
[not found] ` <f600ac1c747813b26c80149b6fdf32d42b114235.1467872014.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-07 7:22 ` Arnd Bergmann
2016-07-07 22:25 ` kbuild test robot [this message]
2016-07-07 6:39 ` [PATCH v4 5/5] ARM: dts: vfxxx: Add a compatible binding for Vybrid SoC bus driver Sanchayan Maity
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=201607080608.ppfp0BMi%fengguang.wu@intel.com \
--to=lkp-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=stefan-XLVq0VzYD2Y@public.gmane.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;
as well as URLs for NNTP newsgroup(s).