From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@suse.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [hare-scsi-devel:tls-upcall.v4 127/156] include/net/tls.h:374:1: error: unknown type name 'key_ref_t'; did you mean 'key_ref_put'?
Date: Sun, 13 Mar 2022 22:35:11 +0800 [thread overview]
Message-ID: <202203132226.RxMqrn2n-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git tls-upcall.v4
head: d2416ecdb6b03fc2e4aa40b20cdf919322713224
commit: 97a450fed0d4ce4978d51685dcca85f9e8b71811 [127/156] net/tls: register '.tls' keyring
config: arc-defconfig (https://download.01.org/0day-ci/archive/20220313/202203132226.RxMqrn2n-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 11.2.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://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git/commit/?id=97a450fed0d4ce4978d51685dcca85f9e8b71811
git remote add hare-scsi-devel https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git
git fetch --no-tags hare-scsi-devel tls-upcall.v4
git checkout 97a450fed0d4ce4978d51685dcca85f9e8b71811
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from net/core/filter.c:79:
>> include/net/tls.h:374:1: error: unknown type name 'key_ref_t'; did you mean 'key_ref_put'?
374 | key_ref_t tls_psk_refresh(char *identity, u8 *data, size_t data_len);
| ^~~~~~~~~
| key_ref_put
include/net/tls.h:375:1: error: unknown type name 'key_ref_t'; did you mean 'key_ref_put'?
375 | key_ref_t tls_psk_lookup(char *identity);
| ^~~~~~~~~
| key_ref_put
vim +374 include/net/tls.h
370
371 int tlsh_pf_create(struct net *net, struct socket *sock, int protocol,
372 int kern);
373
> 374 key_ref_t tls_psk_refresh(char *identity, u8 *data, size_t data_len);
375 key_ref_t tls_psk_lookup(char *identity);
376
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-13 14:36 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=202203132226.RxMqrn2n-lkp@intel.com \
--to=lkp@intel.com \
--cc=hare@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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