From: kernel test robot <lkp@intel.com>
To: Maximilian Luz <luzmaximilian@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, Steev Klimaszewski <steev@kali.org>
Subject: [steev:c630-next-20230303 30/32] include/linux/qcom_qseecom.h:18:10: fatal error: linux/qcom_scm.h: No such file or directory
Date: Sat, 4 Mar 2023 21:11:33 +0800 [thread overview]
Message-ID: <202303042147.EXPBbV3E-lkp@intel.com> (raw)
tree: https://github.com/steev/linux c630-next-20230303
head: d9306ea90cf14a6435578168f594e67096c623ff
commit: 3f9d0114f4032b9d958317ec418a8f83a78bd8ca [30/32] firmware: Add support for Qualcomm UEFI Secure Application
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20230304/202303042147.EXPBbV3E-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.1.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/steev/linux/commit/3f9d0114f4032b9d958317ec418a8f83a78bd8ca
git remote add steev https://github.com/steev/linux
git fetch --no-tags steev c630-next-20230303
git checkout 3f9d0114f4032b9d958317ec418a8f83a78bd8ca
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash drivers/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303042147.EXPBbV3E-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/firmware/qcom_qseecom_uefisecapp.c:16:
>> include/linux/qcom_qseecom.h:18:10: fatal error: linux/qcom_scm.h: No such file or directory
18 | #include <linux/qcom_scm.h>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
vim +18 include/linux/qcom_qseecom.h
34ed78949f2ce7 Maximilian Luz 2023-01-18 12
34ed78949f2ce7 Maximilian Luz 2023-01-18 13 #include <linux/device.h>
34ed78949f2ce7 Maximilian Luz 2023-01-18 14 #include <linux/dma-mapping.h>
34ed78949f2ce7 Maximilian Luz 2023-01-18 15 #include <linux/kernel.h>
34ed78949f2ce7 Maximilian Luz 2023-01-18 16 #include <linux/mm.h>
34ed78949f2ce7 Maximilian Luz 2023-01-18 17 #include <linux/mutex.h>
34ed78949f2ce7 Maximilian Luz 2023-01-18 @18 #include <linux/qcom_scm.h>
34ed78949f2ce7 Maximilian Luz 2023-01-18 19 #include <linux/types.h>
34ed78949f2ce7 Maximilian Luz 2023-01-18 20
34ed78949f2ce7 Maximilian Luz 2023-01-18 21
:::::: The code at line 18 was first introduced by commit
:::::: 34ed78949f2ce7a962ee1073caf2fa5b39852cda firmware: Add support for Qualcomm Secure Execution Environment SCM interface
:::::: TO: Maximilian Luz <luzmaximilian@gmail.com>
:::::: CC: Steev Klimaszewski <steev@kali.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-03-04 13:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202303042147.EXPBbV3E-lkp@intel.com \
--to=lkp@intel.com \
--cc=luzmaximilian@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=steev@kali.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.