From: kernel test robot <lkp@intel.com>
To: Maximilian Luz <luzmaximilian@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v5 2/3] firmware: qcom_scm: Add support for Qualcomm Secure Execution Environment SCM interface
Date: Mon, 31 Jul 2023 01:51:03 +0800 [thread overview]
Message-ID: <202307310104.C9TMGNaM-lkp@intel.com> (raw)
In-Reply-To: <20230730161906.606163-3-luzmaximilian@gmail.com>
Hi Maximilian,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.5-rc3 next-20230728]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Maximilian-Luz/lib-ucs2_string-Add-UCS-2-strscpy-function/20230731-002132
base: linus/master
patch link: https://lore.kernel.org/r/20230730161906.606163-3-luzmaximilian%40gmail.com
patch subject: [PATCH v5 2/3] firmware: qcom_scm: Add support for Qualcomm Secure Execution Environment SCM interface
config: nios2-randconfig-r011-20230730 (https://download.01.org/0day-ci/archive/20230731/202307310104.C9TMGNaM-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230731/202307310104.C9TMGNaM-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202307310104.C9TMGNaM-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
nios2-linux-ld: drivers/firmware/qcom_scm-smc.o: in function `qcom_scm_qseecom_app_get_id':
>> drivers/firmware/qcom_scm-smc.c:136: multiple definition of `qcom_scm_qseecom_app_get_id'; drivers/firmware/qcom_scm.o:qcom_scm.c:(.text+0xc2c): first defined here
nios2-linux-ld: drivers/firmware/qcom_scm-smc.o: in function `qcom_scm_qseecom_app_send':
>> drivers/firmware/qcom_scm-smc.c:142: multiple definition of `qcom_scm_qseecom_app_send'; drivers/firmware/qcom_scm.o:qcom_scm.c:(.text+0xc34): first defined here
nios2-linux-ld: drivers/firmware/qcom_scm-legacy.o: in function `qcom_scm_qseecom_app_get_id':
drivers/firmware/qcom_scm-legacy.c:136: multiple definition of `qcom_scm_qseecom_app_get_id'; drivers/firmware/qcom_scm.o:qcom_scm.c:(.text+0xc2c): first defined here
nios2-linux-ld: drivers/firmware/qcom_scm-legacy.o: in function `qcom_scm_qseecom_app_send':
drivers/firmware/qcom_scm-legacy.c:142: multiple definition of `qcom_scm_qseecom_app_send'; drivers/firmware/qcom_scm.o:qcom_scm.c:(.text+0xc34): first defined here
--
In file included from drivers/firmware/qcom_scm-smc.c:11:
>> include/linux/firmware/qcom/qcom_scm.h:133:5: warning: no previous prototype for 'qcom_scm_qseecom_app_get_id' [-Wmissing-prototypes]
133 | int qcom_scm_qseecom_app_get_id(const char *app_name, u32 *app_id)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/firmware/qcom/qcom_scm.h:138:5: warning: no previous prototype for 'qcom_scm_qseecom_app_send' [-Wmissing-prototypes]
138 | int qcom_scm_qseecom_app_send(u32 app_id, void *req, size_t req_size, void *rsp,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
vim +136 drivers/firmware/qcom_scm-smc.c
6bf32599223634 drivers/firmware/qcom_scm-smc.c Guru Das Srinagesh 2023-01-13 117
6bf32599223634 drivers/firmware/qcom_scm-smc.c Guru Das Srinagesh 2023-01-13 118 static int __scm_smc_do(struct device *dev, struct arm_smccc_args *smc,
3f951ea627dae8 drivers/firmware/qcom_scm-64.c Elliot Berman 2020-01-07 119 struct arm_smccc_res *res, bool atomic)
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 120 {
6bf32599223634 drivers/firmware/qcom_scm-smc.c Guru Das Srinagesh 2023-01-13 121 int ret, retry_count = 0;
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 122
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 123 if (atomic) {
3f951ea627dae8 drivers/firmware/qcom_scm-64.c Elliot Berman 2020-01-07 124 __scm_smc_do_quirk(smc, res);
6bf32599223634 drivers/firmware/qcom_scm-smc.c Guru Das Srinagesh 2023-01-13 125 return 0;
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 126 }
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 127
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 128 do {
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 129 mutex_lock(&qcom_scm_lock);
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 130
6bf32599223634 drivers/firmware/qcom_scm-smc.c Guru Das Srinagesh 2023-01-13 131 ret = __scm_smc_do_quirk_handle_waitq(dev, smc, res);
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 132
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 133 mutex_unlock(&qcom_scm_lock);
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 134
6bf32599223634 drivers/firmware/qcom_scm-smc.c Guru Das Srinagesh 2023-01-13 135 if (ret)
6bf32599223634 drivers/firmware/qcom_scm-smc.c Guru Das Srinagesh 2023-01-13 @136 return ret;
6bf32599223634 drivers/firmware/qcom_scm-smc.c Guru Das Srinagesh 2023-01-13 137
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 138 if (res->a0 == QCOM_SCM_V2_EBUSY) {
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 139 if (retry_count++ > QCOM_SCM_EBUSY_MAX_RETRY)
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 140 break;
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 141 msleep(QCOM_SCM_EBUSY_WAIT_MS);
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 @142 }
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 143 } while (res->a0 == QCOM_SCM_V2_EBUSY);
6bf32599223634 drivers/firmware/qcom_scm-smc.c Guru Das Srinagesh 2023-01-13 144
6bf32599223634 drivers/firmware/qcom_scm-smc.c Guru Das Srinagesh 2023-01-13 145 return 0;
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 146 }
1a5ea3b7a6ac6c drivers/firmware/qcom_scm-64.c Vivek Gautam 2019-09-20 147
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-07-30 17:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 16:19 [PATCH v5 0/3] firmware: Add support for Qualcomm UEFI Secure Application Maximilian Luz
2023-07-30 16:19 ` [PATCH v5 1/3] lib/ucs2_string: Add UCS-2 strscpy function Maximilian Luz
2023-08-03 15:17 ` Bjorn Andersson
2023-08-04 8:18 ` Kees Cook
2023-08-04 19:23 ` Maximilian Luz
2023-07-30 16:19 ` [PATCH v5 2/3] firmware: qcom_scm: Add support for Qualcomm Secure Execution Environment SCM interface Maximilian Luz
2023-07-30 17:51 ` kernel test robot [this message]
2023-07-30 18:04 ` Maximilian Luz
2023-07-30 18:32 ` kernel test robot
2023-07-30 18:42 ` kernel test robot
2023-07-30 18:47 ` Maximilian Luz
2023-08-04 16:48 ` Johan Hovold
2023-08-04 20:11 ` Maximilian Luz
2023-08-07 8:46 ` Johan Hovold
2023-07-30 16:19 ` [PATCH v5 3/3] firmware: Add support for Qualcomm UEFI Secure Application Maximilian Luz
2023-08-03 15:44 ` Ard Biesheuvel
2023-08-03 17:09 ` Maximilian Luz
2023-08-04 10:56 ` Ard Biesheuvel
2023-08-04 16:54 ` Johan Hovold
2023-08-04 19:44 ` Maximilian Luz
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=202307310104.C9TMGNaM-lkp@intel.com \
--to=lkp@intel.com \
--cc=luzmaximilian@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.