From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-nvme@lists.infradead.org,
Keith Busch <kbusch@kernel.org>
Subject: [linux-nvme:nvme-6.19 4/21] include/linux/nvme-keyring.h:57:4: warning: no previous prototype for function 'nvme_dhchap_psk_hash'
Date: Sat, 1 Nov 2025 11:32:15 +0800 [thread overview]
Message-ID: <202511011103.e6eXLAln-lkp@intel.com> (raw)
tree: git://git.infradead.org/nvme.git nvme-6.19
head: 453ba3089d4570c2be2e230e1e7a287eac4b306b
commit: 8d9937531a4d3cb6d2d352c46dd807bfa52988b6 [4/21] nvme-keyring: add 'dhchap' key type
config: x86_64-randconfig-121-20251101 (https://download.01.org/0day-ci/archive/20251101/202511011103.e6eXLAln-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251101/202511011103.e6eXLAln-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/202511011103.e6eXLAln-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/nvme/host/fabrics.c:15:
>> include/linux/nvme-keyring.h:57:4: warning: no previous prototype for function 'nvme_dhchap_psk_hash' [-Wmissing-prototypes]
57 | u8 nvme_dhchap_psk_hash(struct key *key)
| ^
include/linux/nvme-keyring.h:57:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
57 | u8 nvme_dhchap_psk_hash(struct key *key)
| ^
| static
1 warning generated.
vim +/nvme_dhchap_psk_hash +57 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(-ENOTSUPP);
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(-ENOTSUPP);
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(-ENOTSUPP);
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(-ENOTSUPP);
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:[~2025-11-01 3:33 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=202511011103.e6eXLAln-lkp@intel.com \
--to=lkp@intel.com \
--cc=hare@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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 NNTP newsgroup(s).