From: kbuild test robot <lkp@intel.com>
To: Sarangdhar Joshi <spjoshi@codeaurora.org>
Cc: kbuild-all@01.org, Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Sarangdhar Joshi <spjoshi@codeaurora.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Stephen Boyd <sboyd@codeaurora.org>,
Trilok Soni <tsoni@codeaurora.org>
Subject: Re: [PATCH] remoteproc: Remove firmware_loading_complete
Date: Wed, 14 Dec 2016 12:50:34 +0800 [thread overview]
Message-ID: <201612141207.wUX347cO%fengguang.wu@intel.com> (raw)
In-Reply-To: <1481671427-30818-1-git-send-email-spjoshi@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]
Hi Sarangdhar,
[auto build test ERROR on next-20161213]
[also build test ERROR on v4.9]
[cannot apply to remoteproc/for-next v4.9-rc8 v4.9-rc7 v4.9-rc6]
[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/Sarangdhar-Joshi/remoteproc-Remove-firmware_loading_complete/20161214-075027
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
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 errors (new ones prefixed by >>):
drivers/soc/ti/wkup_m3_ipc.c: In function 'wkup_m3_rproc_boot_thread':
>> drivers/soc/ti/wkup_m3_ipc.c:373:36: error: 'struct rproc' has no member named 'firmware_loading_complete'
wait_for_completion(&m3_ipc->rproc->firmware_loading_complete);
^~
vim +373 drivers/soc/ti/wkup_m3_ipc.c
cdd5de50 Dave Gerlach 2015-09-22 367
cdd5de50 Dave Gerlach 2015-09-22 368 static void wkup_m3_rproc_boot_thread(struct wkup_m3_ipc *m3_ipc)
cdd5de50 Dave Gerlach 2015-09-22 369 {
cdd5de50 Dave Gerlach 2015-09-22 370 struct device *dev = m3_ipc->dev;
cdd5de50 Dave Gerlach 2015-09-22 371 int ret;
cdd5de50 Dave Gerlach 2015-09-22 372
cdd5de50 Dave Gerlach 2015-09-22 @373 wait_for_completion(&m3_ipc->rproc->firmware_loading_complete);
cdd5de50 Dave Gerlach 2015-09-22 374
cdd5de50 Dave Gerlach 2015-09-22 375 init_completion(&m3_ipc->sync_complete);
cdd5de50 Dave Gerlach 2015-09-22 376
:::::: The code at line 373 was first introduced by commit
:::::: cdd5de500b2c90d5181ebc963826019a0a4234ba soc: ti: Add wkup_m3_ipc driver
:::::: TO: Dave Gerlach <d-gerlach@ti.com>
:::::: CC: Tony Lindgren <tony@atomide.com>
---
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: 60350 bytes --]
prev parent reply other threads:[~2016-12-14 4:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 23:23 Sarangdhar Joshi
2016-12-14 4:50 ` 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=201612141207.wUX347cO%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=kbuild-all@01.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=sboyd@codeaurora.org \
--cc=spjoshi@codeaurora.org \
--cc=tsoni@codeaurora.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®