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 02:32:23 +0800 [thread overview]
Message-ID: <202307310244.vaA3izJB-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: arc-randconfig-r023-20230731 (https://download.01.org/0day-ci/archive/20230731/202307310244.vaA3izJB-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230731/202307310244.vaA3izJB-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/202307310244.vaA3izJB-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
drivers/firmware/qcom_qseecom.c: In function 'qseecom_client_release':
>> drivers/firmware/qcom_qseecom.c:24:9: error: implicit declaration of function 'kfree' [-Werror=implicit-function-declaration]
24 | kfree(client);
| ^~~~~
drivers/firmware/qcom_qseecom.c: In function 'qseecom_client_register':
>> drivers/firmware/qcom_qseecom.c:50:18: error: implicit declaration of function 'kzalloc' [-Werror=implicit-function-declaration]
50 | client = kzalloc(sizeof(*client), GFP_KERNEL);
| ^~~~~~~
>> drivers/firmware/qcom_qseecom.c:50:16: warning: assignment to 'struct qseecom_client *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
50 | client = kzalloc(sizeof(*client), GFP_KERNEL);
| ^
cc1: some warnings being treated as errors
vim +/kfree +24 drivers/firmware/qcom_qseecom.c
19
20 static void qseecom_client_release(struct device *dev)
21 {
22 struct qseecom_client *client = container_of(dev, struct qseecom_client, aux_dev.dev);
23
> 24 kfree(client);
25 }
26
27 static void qseecom_client_remove(void *data)
28 {
29 struct qseecom_client *client = data;
30
31 auxiliary_device_delete(&client->aux_dev);
32 auxiliary_device_uninit(&client->aux_dev);
33 }
34
35 static int qseecom_client_register(struct platform_device *qseecom_dev,
36 const struct qseecom_app_desc *desc)
37 {
38 struct qseecom_client *client;
39 u32 app_id;
40 int ret;
41
42 /* Try to find the app ID, skip device if not found */
43 ret = qcom_scm_qseecom_app_get_id(desc->app_name, &app_id);
44 if (ret)
45 return ret == -ENOENT ? 0 : ret;
46
47 dev_info(&qseecom_dev->dev, "setting up client for %s\n", desc->app_name);
48
49 /* Allocate and set-up the client device */
> 50 client = kzalloc(sizeof(*client), GFP_KERNEL);
51 if (!client)
52 return -ENOMEM;
53
54 client->aux_dev.name = desc->dev_name;
55 client->aux_dev.dev.parent = &qseecom_dev->dev;
56 client->aux_dev.dev.release = qseecom_client_release;
57 client->app_id = app_id;
58
59 ret = auxiliary_device_init(&client->aux_dev);
60 if (ret) {
61 kfree(client);
62 return ret;
63 }
64
65 ret = auxiliary_device_add(&client->aux_dev);
66 if (ret) {
67 auxiliary_device_uninit(&client->aux_dev);
68 return ret;
69 }
70
71 ret = devm_add_action_or_reset(&qseecom_dev->dev, qseecom_client_remove, client);
72 if (ret)
73 return ret;
74
75 return 0;
76 }
77
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-07-30 18:32 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
2023-07-30 18:04 ` Maximilian Luz
2023-07-30 18:32 ` kernel test robot [this message]
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=202307310244.vaA3izJB-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.