From: kbuild test robot <lkp@intel.com>
To: Stephen Boyd <stephen.boyd@linaro.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mark Brown <broonie@kernel.org>,
Ming Lei <ming.lei@canonical.com>,
Vikram Mulukutla <markivx@codeaurora.org>
Subject: Re: [RESEND/PATCHv4 v4 3/3] firmware: Support loading into a pre-allocated buffer
Date: Sun, 12 Jun 2016 17:28:23 +0800 [thread overview]
Message-ID: <201606121736.x3UpVTjF%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160607164741.31849-4-stephen.boyd@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
Hi,
[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on v4.7-rc2]
[cannot apply to next-20160609]
[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/Stephen-Boyd/firmware-Consolidate-kmap-read-write-logic/20160607-164005
config: x86_64-randconfig-v0-06121632 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
In file included from drivers/video/fbdev/metronomefb.c:33:0:
>> include/linux/firmware.h:82:1: error: expected identifier or '(' before '{' token
{
^
include/linux/firmware.h:80:19: warning: 'request_firmware_into_buf' declared 'static' but never defined [-Wunused-function]
static inline int request_firmware_into_buf(const struct firmware **firmware_p,
^~~~~~~~~~~~~~~~~~~~~~~~~
vim +82 include/linux/firmware.h
76 {
77 return -EINVAL;
78 }
79
80 static inline int request_firmware_into_buf(const struct firmware **firmware_p,
81 const char *name, struct device *device, void *buf, size_t size);
> 82 {
83 return -EINVAL;
84 }
85
---
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: 23402 bytes --]
prev parent reply other threads:[~2016-06-12 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 16:47 [RESEND/PATCHv4 v4 0/3] request_firmware() into pre-allocated buffers Stephen Boyd
2016-06-07 16:47 ` [RESEND/PATCHv4 v4 1/3] firmware: Consolidate kmap/read/write logic Stephen Boyd
2016-06-07 20:21 ` Andrew Morton
2016-06-07 16:47 ` [RESEND/PATCHv4 v4 2/3] firmware: Provide infrastructure to make fw caching optional Stephen Boyd
2016-06-14 1:53 ` Luis R. Rodriguez
2016-06-07 16:47 ` [RESEND/PATCHv4 v4 3/3] firmware: Support loading into a pre-allocated buffer Stephen Boyd
2016-06-12 9:28 ` 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=201606121736.x3UpVTjF%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markivx@codeaurora.org \
--cc=ming.lei@canonical.com \
--cc=stephen.boyd@linaro.org \
--cc=zohar@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).