From: kernel test robot <lkp@intel.com>
To: Deepak Kumar Singh <deesin@codeaurora.org>,
bjorn.andersson@linaro.org, clew@codeaurora.org
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
Deepak Kumar Singh <deesin@codeaurora.org>,
Andy Gross <agross@kernel.org>
Subject: Re: [PATCH V1 1/2] soc: qcom: aoss: Expose send for generic usecase
Date: Fri, 2 Apr 2021 17:50:56 +0800 [thread overview]
Message-ID: <202104021724.aMl0tQz1-lkp@intel.com> (raw)
In-Reply-To: <1617344238-12137-2-git-send-email-deesin@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]
Hi Deepak,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.12-rc5 next-20210401]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Deepak-Kumar-Singh/soc-qcom-aoss-Expose-send-for-generic-usecase/20210402-141935
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 1678e493d530e7977cce34e59a86bb86f3c5631e
config: arc-allyesconfig (attached as .config)
compiler: arceb-elf-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/799aeefaad3e944f54af76e20156de53331f5d3d
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Deepak-Kumar-Singh/soc-qcom-aoss-Expose-send-for-generic-usecase/20210402-141935
git checkout 799aeefaad3e944f54af76e20156de53331f5d3d
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/soc/qcom/qcom_aoss.c:16:10: fatal error: linux/soc/qcom/qcom_aoss.h: No such file or directory
16 | #include <linux/soc/qcom/qcom_aoss.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +16 drivers/soc/qcom/qcom_aoss.c
> 16 #include <linux/soc/qcom/qcom_aoss.h>
17
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 67493 bytes --]
next prev parent reply other threads:[~2021-04-02 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 6:17 [PATCH V1 0/2] soc: qcom: aoss: Expose send for generic usecase Deepak Kumar Singh
2021-04-02 6:17 ` [PATCH V1 1/2] " Deepak Kumar Singh
2021-04-02 9:09 ` kernel test robot
2021-04-02 9:50 ` kernel test robot [this message]
2021-04-04 17:17 ` Bjorn Andersson
2021-04-09 7:31 ` Manivannan Sadhasivam
2021-04-13 0:06 ` Bjorn Andersson
2021-04-02 6:17 ` [PATCH V1 2/2] soc: qcom: aoss: Add debugfs entry Deepak Kumar Singh
2021-04-04 16:59 ` Bjorn Andersson
2021-04-04 17:20 ` [PATCH V1 0/2] soc: qcom: aoss: Expose send for generic usecase Bjorn Andersson
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=202104021724.aMl0tQz1-lkp@intel.com \
--to=lkp@intel.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=clew@codeaurora.org \
--cc=deesin@codeaurora.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@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;
as well as URLs for NNTP newsgroup(s).