From: kernel test robot <lkp@intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Elliot Berman <quic_eberman@quicinc.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Guru Das Srinagesh <quic_gurus@quicinc.com>,
Andrew Halaney <ahalaney@redhat.com>,
Maximilian Luz <luzmaximilian@gmail.com>,
Alex Elder <elder@linaro.org>,
Srini Kandagatla <srinivas.kandagatla@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@quicinc.com,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v3 11/15] firmware: qcom: qseecom: convert to using the TZ allocator
Date: Fri, 13 Oct 2023 07:21:25 +0800 [thread overview]
Message-ID: <202310130731.YHBtmaQU-lkp@intel.com> (raw)
In-Reply-To: <20231009153427.20951-12-brgl@bgdev.pl>
Hi Bartosz,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20231009]
[cannot apply to arm64/for-next/core krzk-dt/for-next linus/master v6.6-rc5 v6.6-rc4 v6.6-rc3 v6.6-rc5]
[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/Bartosz-Golaszewski/firmware-qcom-move-Qualcomm-code-into-its-own-directory/20231009-233826
base: next-20231009
patch link: https://lore.kernel.org/r/20231009153427.20951-12-brgl%40bgdev.pl
patch subject: [PATCH v3 11/15] firmware: qcom: qseecom: convert to using the TZ allocator
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20231013/202310130731.YHBtmaQU-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231013/202310130731.YHBtmaQU-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/202310130731.YHBtmaQU-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/firmware/qcom/qcom_qseecom_uefisecapp.c: In function 'qcom_uefisecapp_probe':
>> drivers/firmware/qcom/qcom_qseecom_uefisecapp.c:767:67: error: 'SZ_256K' undeclared (first use in this function)
767 | qcuefi->mempool = devm_qcom_tzmem_pool_new(&aux_dev->dev, SZ_256K);
| ^~~~~~~
drivers/firmware/qcom/qcom_qseecom_uefisecapp.c:767:67: note: each undeclared identifier is reported only once for each function it appears in
vim +/SZ_256K +767 drivers/firmware/qcom/qcom_qseecom_uefisecapp.c
745
746 static int qcom_uefisecapp_probe(struct auxiliary_device *aux_dev,
747 const struct auxiliary_device_id *aux_dev_id)
748 {
749 struct qcuefi_client *qcuefi;
750 int status;
751
752 qcuefi = devm_kzalloc(&aux_dev->dev, sizeof(*qcuefi), GFP_KERNEL);
753 if (!qcuefi)
754 return -ENOMEM;
755
756 qcuefi->client = container_of(aux_dev, struct qseecom_client, aux_dev);
757
758 auxiliary_set_drvdata(aux_dev, qcuefi);
759 status = qcuefi_set_reference(qcuefi);
760 if (status)
761 return status;
762
763 status = efivars_register(&qcuefi->efivars, &qcom_efivar_ops);
764 if (status)
765 qcuefi_set_reference(NULL);
766
> 767 qcuefi->mempool = devm_qcom_tzmem_pool_new(&aux_dev->dev, SZ_256K);
768 if (IS_ERR(qcuefi->mempool))
769 return PTR_ERR(qcuefi->mempool);
770
771 return status;
772 }
773
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-12 23:23 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 15:34 [PATCH v3 00/15] arm64: qcom: add and enable SHM Bridge support Bartosz Golaszewski
2023-10-09 15:34 ` [PATCH v3 01/15] firmware: qcom: move Qualcomm code into its own directory Bartosz Golaszewski
2023-10-11 20:01 ` Maximilian Luz
2023-10-09 15:34 ` [PATCH v3 02/15] firmware: qcom: scm: add a missing forward declaration for struct device Bartosz Golaszewski
2023-10-10 19:44 ` Andrew Halaney
2023-10-09 15:34 ` [PATCH v3 03/15] firmware: qcom: scm: remove unneeded 'extern' specifiers Bartosz Golaszewski
2023-10-10 19:45 ` Andrew Halaney
2023-10-09 15:34 ` [PATCH v3 04/15] firmware: qcom: add a dedicated TrustZone buffer allocator Bartosz Golaszewski
2023-10-09 21:28 ` Andrew Halaney
2023-10-10 6:42 ` Bartosz Golaszewski
2023-10-10 8:26 ` Bartosz Golaszewski
2023-10-10 20:48 ` Andrew Halaney
2023-10-11 7:39 ` Bartosz Golaszewski
2023-10-09 15:34 ` [PATCH v3 05/15] firmware: qcom: scm: enable the TZ mem allocator Bartosz Golaszewski
2023-10-10 9:11 ` kernel test robot
2023-10-09 15:34 ` [PATCH v3 06/15] firmware: qcom: scm: smc: switch to using the SCM allocator Bartosz Golaszewski
2023-10-10 22:12 ` Andrew Halaney
2023-10-09 15:34 ` [PATCH v3 07/15] firmware: qcom: scm: make qcom_scm_assign_mem() use the TZ allocator Bartosz Golaszewski
2023-10-10 22:19 ` Andrew Halaney
2023-10-11 7:41 ` Bartosz Golaszewski
2023-10-11 13:54 ` Andrew Halaney
2023-10-11 14:33 ` Bartosz Golaszewski
2023-10-11 20:13 ` Andrew Halaney
2023-10-09 15:34 ` [PATCH v3 08/15] firmware: qcom: scm: make qcom_scm_ice_set_key() " Bartosz Golaszewski
2023-10-10 22:25 ` Andrew Halaney
2023-10-09 15:34 ` [PATCH v3 09/15] firmware: qcom: scm: make qcom_scm_lmh_dcvsh() " Bartosz Golaszewski
2023-10-10 22:26 ` Andrew Halaney
2023-10-09 15:34 ` [PATCH v3 10/15] firmware: qcom: scm: make qcom_scm_qseecom_app_get_id() " Bartosz Golaszewski
2023-10-10 22:28 ` Andrew Halaney
2023-10-11 20:09 ` Maximilian Luz
2023-10-09 15:34 ` [PATCH v3 11/15] firmware: qcom: qseecom: convert to using " Bartosz Golaszewski
2023-10-10 22:49 ` Andrew Halaney
2023-10-11 7:44 ` Bartosz Golaszewski
2023-10-11 13:55 ` Andrew Halaney
2023-10-11 14:37 ` Bartosz Golaszewski
2023-10-11 20:47 ` Maximilian Luz
2023-10-11 20:09 ` Maximilian Luz
2023-10-12 23:21 ` kernel test robot [this message]
2023-10-09 15:34 ` [PATCH v3 12/15] firmware: qcom: scm: add support for SHM bridge operations Bartosz Golaszewski
2023-10-09 15:34 ` [PATCH v3 13/15] firmware: qcom: tzmem: enable SHM Bridge support Bartosz Golaszewski
2023-10-11 21:14 ` Andrew Halaney
2023-10-11 22:17 ` Andrew Halaney
2023-10-13 8:32 ` Bartosz Golaszewski
2023-10-13 13:30 ` Andrew Halaney
2023-10-13 14:06 ` Bartosz Golaszewski
2023-10-09 15:34 ` [PATCH v3 14/15] firmware: qcom: scm: clarify the comment in qcom_scm_pas_init_image() Bartosz Golaszewski
2023-10-11 21:19 ` Andrew Halaney
2023-10-09 15:34 ` [PATCH v3 15/15] arm64: defconfig: enable SHM Bridge support for the TZ memory allocator Bartosz Golaszewski
2023-10-11 21:20 ` Andrew Halaney
2023-10-12 8:57 ` Bartosz Golaszewski
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=202310130731.YHBtmaQU-lkp@intel.com \
--to=lkp@intel.com \
--cc=agross@kernel.org \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=elder@linaro.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_eberman@quicinc.com \
--cc=quic_gurus@quicinc.com \
--cc=srinivas.kandagatla@linaro.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).