From: kernel test robot <lkp@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jarkko-tpmdd:tpm2_key 39/39] mips-linux-ld: tpm2_key.c:undefined reference to `asn1_encode_integer'
Date: Tue, 14 May 2024 04:40:52 +0800 [thread overview]
Message-ID: <202405140411.ds33krlP-lkp@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tpm2_key
head: 3ab444ea2fe8b38de7ffe05aacbf22b664c8f115
commit: c9b223b1ac3db418fc3ab49d007b5a12f8b091aa [39/39] crypto: Add foundations for TPM2 asymmetric keys
config: mips-randconfig-r081-20240513 (https://download.01.org/0day-ci/archive/20240514/202405140411.ds33krlP-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240514/202405140411.ds33krlP-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/202405140411.ds33krlP-lkp@intel.com/
All errors (new ones prefixed by >>):
mips-linux-ld: drivers/char/tpm/tpm2_key.o: in function `tpm2_key_encode':
tpm2_key.c:(.text+0x200): undefined reference to `asn1_encode_oid'
>> mips-linux-ld: tpm2_key.c:(.text+0x238): undefined reference to `asn1_encode_integer'
>> mips-linux-ld: tpm2_key.c:(.text+0x24c): undefined reference to `asn1_encode_octet_string'
mips-linux-ld: tpm2_key.c:(.text+0x260): undefined reference to `asn1_encode_octet_string'
>> mips-linux-ld: tpm2_key.c:(.text+0x274): undefined reference to `asn1_encode_sequence'
>> mips-linux-ld: tpm2_key.c:(.text+0x2e8): undefined reference to `asn1_encode_boolean'
>> mips-linux-ld: tpm2_key.c:(.text+0x314): undefined reference to `asn1_encode_tag'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-13 20:41 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=202405140411.ds33krlP-lkp@intel.com \
--to=lkp@intel.com \
--cc=jarkko@kernel.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).