From: kernel test robot <lkp@intel.com>
To: Masahisa Kojima <masahisa.kojima@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 2/2] tee: Add op-tee helper functions for variable access
Date: Sun, 29 Jan 2023 10:08:14 +0800 [thread overview]
Message-ID: <202301290936.Tla4Ic8d-lkp@intel.com> (raw)
In-Reply-To: <20230126132120.1661-3-masahisa.kojima@linaro.org>
Hi Masahisa,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on efi/next]
[also build test ERROR on next-20230127]
[cannot apply to linus/master v6.2-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/Masahisa-Kojima/efi-expose-efivar-generic-ops-register-function/20230128-170022
base: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next
patch link: https://lore.kernel.org/r/20230126132120.1661-3-masahisa.kojima%40linaro.org
patch subject: [RFC PATCH 2/2] tee: Add op-tee helper functions for variable access
config: arm-randconfig-r046-20230129 (https://download.01.org/0day-ci/archive/20230129/202301290936.Tla4Ic8d-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/intel-lab-lkp/linux/commit/2ff56d7a5b6fa1214c4ef504b921b52d387e0e3b
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Masahisa-Kojima/efi-expose-efivar-generic-ops-register-function/20230128-170022
git checkout 2ff56d7a5b6fa1214c4ef504b921b52d387e0e3b
# 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
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arm-linux-gnueabi-ld: drivers/tee/tee_core.o: in function `tee_register_efivar_ops':
>> tee_core.c:(.text+0x1122): undefined reference to `efivar_supports_writes'
>> arm-linux-gnueabi-ld: tee_core.c:(.text+0x1132): undefined reference to `efivars_generic_ops_unregister'
arm-linux-gnueabi-ld: drivers/tee/tee_core.o: in function `tee_unregister_efivar_ops':
>> tee_core.c:(.text+0x114e): undefined reference to `efivars_unregister'
arm-linux-gnueabi-ld: drivers/tee/tee_core.o: in function `tee_register_efivar_ops':
>> tee_core.c:(.text+0x113e): undefined reference to `efivars_register'
arm-linux-gnueabi-ld: drivers/tee/tee_core.o: in function `tee_unregister_efivar_ops':
>> tee_core.c:(.text+0x1156): undefined reference to `efivars_generic_ops_register'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-01-29 2:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 13:21 [RFC PATCH 0/2] introduce op-tee based EFI Runtime Variable Service Masahisa Kojima
2023-01-26 13:21 ` Masahisa Kojima
2023-01-26 13:21 ` [RFC PATCH 1/2] efi: expose efivar generic ops register function Masahisa Kojima
2023-01-26 13:21 ` Masahisa Kojima
2023-01-26 13:21 ` [RFC PATCH 2/2] tee: Add op-tee helper functions for variable access Masahisa Kojima
2023-01-26 13:21 ` Masahisa Kojima
2023-01-26 13:21 ` Masahisa Kojima
2023-01-29 2:08 ` kernel test robot [this message]
2023-01-29 3:41 ` kernel test robot
2023-02-03 9:30 ` Jens Wiklander
2023-02-03 9:30 ` Jens Wiklander
2023-02-03 9:30 ` Jens Wiklander
2023-02-06 6:08 ` Masahisa Kojima
2023-02-06 6:08 ` Masahisa Kojima
2023-02-06 6:08 ` Masahisa Kojima
2023-02-02 12:05 ` [RFC PATCH 0/2] introduce op-tee based EFI Runtime Variable Service Sumit Garg
2023-02-02 12:05 ` Sumit Garg
[not found] < <CAFA6WYMdTxkcFkSux7F3fwxx2OqHP9UzqbWxdGnxuzjNU75PxA@mail.gmail.com>
2023-02-02 13:19 ` Ilias Apalodimas
2023-02-02 13:19 ` Ilias Apalodimas
2023-02-03 8:29 ` Jens Wiklander
2023-02-03 8:29 ` Jens Wiklander
2023-02-03 9:33 ` Sumit Garg
2023-02-03 9:33 ` Sumit Garg
[not found] < <CAFA6WYOp-NQxvqOmemiW2D5Au549f-u4LJA7XEK2aJgMiXRUYg@mail.gmail.com>
2023-02-03 10:55 ` Jens Wiklander
2023-02-03 10:55 ` Jens Wiklander
2023-02-06 6:44 ` Sumit Garg
2023-02-06 6:44 ` Sumit Garg
[not found] < <CAFA6WYPLeN5tUY8JA=J9T3XVNfq5jAQ62i=qSk-6eesM-9_K=Q@mail.gmail.com>
2023-02-06 7:47 ` Jens Wiklander
2023-02-06 7:47 ` Jens Wiklander
2023-02-06 9:22 ` Ard Biesheuvel
2023-02-06 9:22 ` Ard Biesheuvel
2023-02-06 9:31 ` Ilias Apalodimas
2023-02-06 9:31 ` Ilias Apalodimas
[not found] < <CAMj1kXGg3wwhJFRjAGEP2fDLcbHpiuHuiaW2y+oVgjwULqVTZg@mail.gmail.com>
2023-02-06 11:11 ` Sumit Garg
2023-02-06 11:11 ` Sumit Garg
[not found] < <CAFA6WYO5r66VqdczFH4HC1O=DuuauQBohr80zPLA86rnHgC48Q@mail.gmail.com>
2023-02-20 5:01 ` Masahisa Kojima
2023-02-20 5:01 ` Masahisa Kojima
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=202301290936.Tla4Ic8d-lkp@intel.com \
--to=lkp@intel.com \
--cc=masahisa.kojima@linaro.org \
--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.