From: kbuild test robot <lkp@intel.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/4] v4l: vsp1: Add Cubic Look Up Table (CLU) support
Date: Mon, 16 Nov 2015 06:10:45 +0000 [thread overview]
Message-ID: <201511161417.7lAdsqY9%fengguang.wu@intel.com> (raw)
In-Reply-To: <1447649205-1560-3-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
[-- Attachment #1: Type: text/plain, Size: 2498 bytes --]
Hi Laurent,
[auto build test ERROR on: renesas/next]
[also build test ERROR on: v4.4-rc1 next-20151116]
url: https://github.com/0day-ci/linux/commits/Laurent-Pinchart/VSP1-Add-support-for-lookup-tables/20151116-124808
base: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next
config: x86_64-randconfig-s5-11161354 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All error/warnings (new ones prefixed by >>):
drivers/media/platform/vsp1/vsp1_clu.c: In function 'clu_configure':
>> drivers/media/platform/vsp1/vsp1_clu.c:48:12: error: implicit declaration of function 'kcalloc' [-Werror=implicit-function-declaration]
entries = kcalloc(config->nentries, sizeof(*entries), GFP_KERNEL);
^
>> drivers/media/platform/vsp1/vsp1_clu.c:48:10: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
entries = kcalloc(config->nentries, sizeof(*entries), GFP_KERNEL);
^
>> drivers/media/platform/vsp1/vsp1_clu.c:77:2: error: implicit declaration of function 'kfree' [-Werror=implicit-function-declaration]
kfree(entries);
^
cc1: some warnings being treated as errors
vim +/kcalloc +48 drivers/media/platform/vsp1/vsp1_clu.c
42 unsigned int i;
43 int ret;
44
45 if (config->nentries > 17*17*17)
46 return -EINVAL;
47
> 48 entries = kcalloc(config->nentries, sizeof(*entries), GFP_KERNEL);
49 if (!entries)
50 return -ENOMEM;
51
52 ret = copy_from_user(entries, config->entries,
53 config->nentries * sizeof(*entries));
54 if (ret) {
55 ret = -EFAULT;
56 goto done;
57 }
58
59 for (i = 0; i < config->nentries; ++i) {
60 u32 addr = entries[i].addr;
61 u32 value = entries[i].value;
62
63 if (((addr >> 0) & 0xff) >= 17 ||
64 ((addr >> 8) & 0xff) >= 17 ||
65 ((addr >> 16) & 0xff) >= 17 ||
66 ((addr >> 24) & 0xff) != 0 ||
67 (value & 0xff000000) != 0) {
68 ret = -EINVAL;
69 goto done;
70 }
71
72 vsp1_clu_write(clu, VI6_CLU_ADDR, addr);
73 vsp1_clu_write(clu, VI6_CLU_DATA, value);
74 }
75
76 done:
> 77 kfree(entries);
78 return ret;
79 }
80
---
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: 22681 bytes --]
next prev parent reply other threads:[~2015-11-16 6:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 4:46 [PATCH 0/4] VSP1: Add support for lookup tables Laurent Pinchart
2015-11-16 4:46 ` [PATCH 1/4] v4l: vsp1: Fix LUT format setting Laurent Pinchart
2015-11-16 4:46 ` [PATCH 2/4] v4l: vsp1: Add Cubic Look Up Table (CLU) support Laurent Pinchart
2015-11-16 6:10 ` kbuild test robot [this message]
2015-11-16 4:46 ` [PATCH 3/4] ARM: Renesas: r8a7790: Enable CLU support in VSPS Laurent Pinchart
2015-11-16 4:46 ` [PATCH 4/4] ARM: Renesas: r8a7791: " Laurent Pinchart
2015-11-24 2:41 ` [PATCH 0/4] VSP1: Add support for lookup tables Simon Horman
2015-11-24 23:50 ` Laurent Pinchart
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=201511161417.7lAdsqY9%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=linux-sh@vger.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