From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [hare-nvme:dhchap-keyring.v4 3/9] include/linux/nvme-keyring.h:54:1: error: expected identifier or '(' before '{' token
Date: Fri, 20 Nov 2026 15:44:46 +0100 [thread overview]
Message-ID: <20261120153351.AVFMzFoj-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hare/nvme.git dhchap-keyring.v4
head: 1b78746d90bfa570d96e88475983421f24c38b0d
commit: a4ba99532949b46aa13cd6d71ccf791cbd692390 [3/9] nvme-auth: switch to use 'struct key'
config: xtensa-randconfig-2200-20261120 (https://download.01.org/0day-ci/archive/20261120/20261120153351.AVFMzFoj-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 9.5.0
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261120/20261120153351.AVFMzFoj-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/20261120153351.AVFMzFoj-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
In file included from drivers/nvme/target/configfs.c:19:
>> include/linux/nvme-keyring.h:54:1: error: expected identifier or '(' before '{' token
54 | {
| ^
>> include/linux/nvme-keyring.h:57:4: warning: no previous prototype for 'nvme_dhchap_psk_hash' [-Wmissing-prototypes]
57 | u8 nvme_dhchap_psk_hash(struct key *key)
| ^~~~~~~~~~~~~~~~~~~~
>> include/linux/nvme-keyring.h:52:27: warning: 'nvme_dhchap_psk_lookup' declared 'static' but never defined [-Wunused-function]
52 | static inline struct key *nvme_dhchap_psk_lookup(struct key *keyring,
| ^~~~~~~~~~~~~~~~~~~~~~
vim +54 include/linux/nvme-keyring.h
26
27 #else
28 static inline struct key *nvme_tls_psk_refresh(struct key *keyring,
29 u8 *data, size_t data_len, const char *digest)
30 {
31 return ERR_PTR(-EOPNOTSUPP);
32 }
33 static inline key_serial_t nvme_tls_psk_default(struct key *keyring,
34 const char *hostnqn, const char *subnqn)
35 {
36 return 0;
37 }
38 static inline key_serial_t nvme_keyring_id(void)
39 {
40 return 0;
41 }
42 static inline struct key *nvme_tls_key_lookup(key_serial_t key_id)
43 {
44 return ERR_PTR(-EOPNOTSUPP);
45 }
46 static inline struct key *nvme_dhchap_psk_refresh(struct key *keyring,
47 const char *hostnqn, const char *subnqn,
48 u8 *data, size_t data_len)
49 {
50 return ERR_PTR(-EOPNOTSUPP);
51 }
> 52 static inline struct key *nvme_dhchap_psk_lookup(struct key *keyring,
53 const char *hostnqn, const char *subnqn, u8 hmac);
> 54 {
55 return ERR_PTR(-EOPNOTSUPP);
56 }
> 57 u8 nvme_dhchap_psk_hash(struct key *key)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-20 14:44 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=20261120153351.AVFMzFoj-lkp@intel.com \
--to=lkp@intel.com \
--cc=hare@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 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.